Some possible bugs I just noticed

[rupertotorres1]

• I don't know if this is how it's supposed to be, but when you take a picture, two files seem to be saved to internal storage: the original picture and the compressed one. When you load a picture from library, only the compressed one seems to be saved to internal storage.

• Pressing take a picture and then pressing return before selecting the checkmark (that you approve the photo or something) doesn't actually delete the temp file: an empty file still appears in internal storage.

• When you take a picture or add from library but press return before saving in the Info screen, the picture doesn't appear in the app browser (desired behaviour, I guess) but it's saved to internal storage (probably shouldn't happen).

• When you delete pictures from the app, they still remain in internal storage.

[vpnda]

I don't know if this is how it's supposed to be, but when you take a picture, two files seem to be saved to internal storage: the original picture and the compressed one. When you load a picture from library, only the compressed one seems to be saved to internal storage.

Up to my knowledge that's how its supposed to be, that's why we use magical URL :D

Pressing take a picture and then pressing return before selecting the checkmark (that you approve the photo or something) doesn't actually delete the temp file: an empty file still appears in internal storage.

How can you know this? I'm trying to figure out where that might happen but I don't see where.

When you take a picture or add from library but press return before saving in the Info screen, the picture doesn't appear in the app browser (desired behaviour, I guess) but it's saved to internal storage (probably shouldn't happen).

Why not? we remove any trace of it when returning

When you delete pictures from the app, they still remain in internal storage.

Again, dunno how that can happen given that we always call the same function to delete them from the database & from our internal storage.

[rupertotorres1]

Up to my knowledge that's how its supposed to be, that's why we use magical URL :D

Hmmm but do we ever use the original one? If we only use compressed ones, maybe it would be better if we found a way to only store the compressed ones?

How can you know this? I'm trying to figure out where that might happen but I don't see where.

In my phone, I can go to Internal Storage -> Android -> data -> com.example.ubclaunchpad.launchnote -> files -> Pictures and see them.

Again, dunno how that can happen given that we always call the same function to delete them from the database & from our internal storage.

Not sure. It seems like deleting from internal storage in general doesn't work. Maybe by fixing that, bullet points 2,3, and 4 would all be fixed.