Sorry, I confused things here. I was not able to install on a Galaxy S1 (Android 2.3.6) but was able to install it on my S3. (I said to you S4 on the email, but it was on a S3).
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
Sorry about the delay, but we have heard back from users since trying the “READ” permission fix. It does not fix our issue. Latest request for a refund is from a user on an S3. Any other ideas as to what this could be?
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.
Hi Martijn,
Just curious, could you reproduce this via samsung’s remote test lab? If so, on what device/setup?
Frustrating that this issue does not seem to be getting any closer to a solution.
Thanks,
David
@playthisstudio.
It still happens, but dont waste your energy, I have been reporting this bug since more than one year and half ago.
I have reported it like 3 times.
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
I’m pretty sure the READ_EXTERNAL_STORAGE permission will resolve the issue that @zabace brought up in this forum, because this issue was only happening on an Android 4.4 device he was testing with. Older versions were fine. We confirmed this with an Android 4.4 device on our end too.
If you’re still running into a photo selection issue, then odds are it’s because the device has the “Developer Option” named “Do no keep activities” checked on under the device’s main Settings. That option will exit the last activity displayed when navigating forward to another activity or to the home screen, which is the equivalent to an “applicationExit” in Corona. So, what you’ll see is that when the end-user finishes making the photo selection, you’ll notice that Corona restarts when returning back from the photo gallery because the Android OS forcibly destroyed the activity and then re-created. When that happens, we have no means of acquiring the last selected photo from the native code level because our onActivityResult() method in Java (which provides the photo selected by the end-user) never gets called.
Hi,
Can anyone confim this? These rights do not seem to solve the issue with selectPhoto and the Gallery. An Image is not selected. While it does work for Photos.
We have tested with http://developer.samsung.com/remotetestlab/rtlDeviceList.action real devices and free testing via Samsung. I’ll look into this developer setting.
But we are also experiencing bad reviews becuase of this from Samssung Galaxy Note and S5 users amongst others. We have over 10,000 download of our app and about 20+ negative reviews related to this specific issue and memory related problems.
Contact us at martijn@igenapps.com If you can shed any light on this.
Thanks,
Martijn
iGenApps
Just tested the developer setting for closing activities, but it had no effect on a Samsung Galaxy note 3 with 4.4.2.
Can it be that intent filters might help here? Or should we use an Android plugin for Corona Enterprise.
Our app is here by the way. https://play.google.com/store/apps/details?id=com.xpous.myapps
Martijn
Tried to download on my Galaxy S3 (which is one model that is famous to show that bug) and it is showing here that my device is not compatible. Did you block that model from the available devices?