I’ll flag this issue to be re-tested on our end too.
We used to be able to reproduce this issue with our “Media/PhotoPicker” sample app. We’ll use that for our testing. Zabace, would you mind testing that sample app on your Galaxy Note 3 too please? I’m curious if this is the same issue we’ve solved or if you’re actually running into something else.
Everyone,
We were able to reproduce this issue on a Barnes&Noble Galaxy Tab 4, which is an Android 4.4 device.
We were unable to reproduce this issue on Android devices older than 4.4.
So, it looks like the issue found might only happen with 4.4 devices or perhaps just with Samsung’s newest Photo Gallery app. I’ve noticed that the new photo gallery app pops up while the current app is still being displayed in the background (new behavior; gallery apps typically display fullscreen via an Android activity). So, I suspect that this new photo app is delivering the selected photo in a different way (ie: different Android intent parameter). That is, this issue does not appear to be related to the memory leak issue mentioned earlier in this forum thread.
Please note that we’re currently guessing that this is a 4.4 only issue. More testing is needed on our end, but it’s in the queue.
Thanks for reporting this issue.
good to know.
Thanks for reporting @zabace
I have been reporting this problem during years. Always the same answer. " We were able to reproduce and we need more test."
I have samsung galaxy s3 and happens
Just fyi, this issue is happening when opening the native camera app as well as the gallery.
zabace,
Is this issue only happening on your Galaxy Note 4?
If it’s happening on your other devices, then can you tell me what their models and OS versions are please?
Thanks in advance.
The only device on which we’ve observed this behavior is a Galaxy Note 3. We’ve tried a Galaxy S3, Galaxy S4, and a Nexus 5, but the problem does not occur on these devices.
I have been reporting this problem since more than one year ago. I have been ignored. Always with the same answer. It happens. And I have a samsung galaxy s3 and it happens. My users have differents devices and they have reported it too.
But of course. It doesnt exist. And we invented this bug.
Is there any progress on this? We have an app out there that is getting a few people here and there having the same issue (app restarting after entering media picker). The latest one was on an S3. This is frustrating as it is out of our control to fix and/or explain to customers.
Another example this morning - this time a video was sent by an unhappy customer showing that the app resets when trying to come back from either camera or photo gallery.
See video here: http://goo.gl/c8cdKC
Is there any way to get this prioritized? And could this forum thread be renamed to remove the [Resolved] please?
David
Another reply from a customer today with details: (Same issue of app restarting on camera or photo gallery)
1.samsung tab 3 7.0
2.android 4.1.2
3.factory mods
4.original gallery
5.meld version 1.10
Im sorry i dont have any picture
I have try to uninstall it and install it back but same problem occur…please fix this…this apps is such a great apps
Can I get some response from Corona on this please?
David
Is there a bug report number that I can look up?
If not, can you file one please?
Thanks
Rob
Thanks Rob,
Bug just entered as I thought this was already on the books - please see (Case 35891). I have attached as much info as I can glean from several customers to it.
David
There may be a bug or there may be one we think we fixed.
Rob
Ok, which build was the fix in? I have been watching daily builds since 2393 and haven’t seen anything about this mentioned. Would be great if I just missed it!
I was referring to the fix this thread talked about earlier. If it’s still happening with with the current daily or public build, then it could be a new bug or the same one with different things causing it.
Rob
Ah, ok, I am referring to Joshua’s post dated 27Aug 2:31 pm where he says:
“So, it looks like the issue found might only happen with 4.4 devices or perhaps just with Samsung’s newest Photo Gallery app. I’ve noticed that the new photo gallery app pops up while the current app is still being displayed in the background (new behavior; gallery apps typically display fullscreen via an Android activity). So, I suspect that this new photo app is delivering the selected photo in a different way (ie: different Android intent parameter). That is, this issue does not appear to be related to the memory leak issue mentioned earlier in this forum thread.”
This (on the face of it) looks like what we are seeing.
Everyone,
Regarding the last mentioned photo issue. We’ve concluded that it’s not a bug, but an Android permission issue on Android OS 4.1 or newer devices. You’ll need to add an “android.permission.READ_EXTERNAL_STORAGE” permission to your “build.settings” in order to resolve this issue. Note that this won’t happen on all Android 4.1 or newer device. It all depends if the Gallery app (or whichever photo app you select) stores photos on external storage or not.
We’ve updated the Corona Simulator’s “Media/PhotoPicker” sample app’s “build.settings” file to make it work on these newer devices.
We’ve also updated our documentation here…
http://docs.coronalabs.com/api/library/media/selectPhoto.html
Thanks Joshua,
I’ll update our build tonight and get it out to a couple of the users that had this issue. Will let you know if that solves their problem. Thanks for looking into this.
David
Hi Joshua,
We are awaiting confirmation from a tester, but in the meantime I have looked and it seems that if you declare “android.permission.WRITE_EXTERNAL_STORAGE”, (which we do) then according to google’s docs, the READ permisssion is “Any app that declares the WRITE_EXTERNAL_STORAGE permission is implicitly granted this permission.”. And having looked at our current apk on the google store, the READ and WRITE permissions are both listed separately.
So I will obviously confirm with tester, but I am not confident this solution is going to address the issue we are seeing.
David