dingo,
Can you check which Android API Level that you are targeting? You can find out by looking at your “AndroidManifest.xml” file at the top and see the <uses-sdk android:targetSdkVersion""> tag. If it is set to 17 or higher (not Corona’s default), then Google has introduced a breaking change where you have to explicitly “export” the content provider as instructed here…
http://developer.android.com/guide/topics/manifest/provider-element.html#exported
Hi Joshua. Thanks for the reply.
I was not able to reproduce that error. I have 4 errors of that type being reported in my Google Dev Console… one of them is also related to the FileContentProvider but also appeared with an extra info: “Didn’t find class “com.ansca.corona.FileContentProvider” on path: /mnt/asec/com.redbeachgames.cutmypuzzle-2/pkg.apk”.
My game bundle is “com.redbeachgames.cutmypuzzle” and not “com.redbeachgames.cutmypuzzle-2”, so may be someone is hacking it?
java.lang.RuntimeException: Unable to get provider com.ansca.corona.FileContentProvider: java.lang.ClassNotFoundException: Didn't find class "com.ansca.corona.FileContentProvider" on path: /mnt/asec/com.redbeachgames.cutmypuzzle-2/pkg.apk at android.app.ActivityThread.installProvider(ActivityThread.java:5033) at android.app.ActivityThread.installContentProviders(ActivityThread.java:4638) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4576) at android.app.ActivityThread.access$1400(ActivityThread.java:152) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1342) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:5328) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1102) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:869) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.ClassNotFoundException: Didn't find class "com.ansca.corona.FileContentProvider" on path: /mnt/asec/com.redbeachgames.cutmypuzzle-2/pkg.apk at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:65) at java.lang.ClassLoader.loadClass(ClassLoader.java:501) at java.lang.ClassLoader.loadClass(ClassLoader.java:461) at android.app.ActivityThread.installProvider(ActivityThread.java:5018) ... 12 moreHmm… yeah, if someone decompiled your APK and then recompiled it targeting Android API Level 17, then I would expect an error to occur. This is because Google made a breaking change with content providers in API Level 17. Corona currently targets API Level 16. We’ve tested the newest daily builds of Corona on Android 4.2 (aka: API Level 17) and 4.3 (API Level 18) devices and haven’t experienced any crashes. I’m really not sure what else could cause ClassNotFoundException error.
Did the crash reports happen to mention what devices these errors occurred on?
Renato,
We think we’ve reproduce the issue that you’ve posted. It tuns out that Android 4.3 will create app directories ending with “-1”, “-2”, “-3”, etc. for different user accounts on a tablet. Meaning that every user account will get their own application directory.
We’ve also discovered that a Corona made app will crash or show a black screen on startup if it is targeting Google Play and it is ran by a restricted user on an Android 4.3 device. The crash will also only happen if the app was installed before the 2nd user account is created. Meaning that the crash will not happen if the app is installed or re-installed after the 2nd user account is created.
Now, we were not getting a ClassNotFoundException that you posted up above, but we were getting a library not found error along with a Lua stack trace. Not the same issue as yours, but I’m wondering if you’re running into a similar issue.
In any case, the Android 4.3 crash that I’ve mentioned has been fixed and will be made available in daily build #1199.
Hi Joshua.
Thanks for getting back to me. Sorry I did not answered you, I looked at my Google Dev Console and I didn’t find the device model that was showing that error (It allows me to filter per device, so Google has that info… but since it has hundred of devices in the filter list, it will take my forever to discover what is the buggy device…).
I looked here and I am not getting that library not found error, but it is good to know that this problem will be fixed in the #1199 daily build. I am updating my games this week, so I will wait this daily build.
Another Android error that I am seeing here is the following:
java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState at android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1286) at android.app.FragmentManagerImpl.popBackStackImmediate(FragmentManager.java:451) at android.app.Activity.onBackPressed(Activity.java:2123) at android.app.Activity.onKeyUp(Activity.java:2101) at com.ansca.corona.CoronaActivity.onKeyUp(CoronaActivity.java:1786) at android.view.KeyEvent.dispatch(KeyEvent.java:2577) at android.app.Activity.dispatchKeyEvent(Activity.java:2334) at com.ansca.corona.input.RaiseKeyEventTask$1.run(RaiseKeyEventTask.java:87) at android.os.Handler.handleCallback(Handler.java:605) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:4424) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:817) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584) at dalvik.system.NativeStart.main(Native Method)
It appears to me that is more related to the device instead of the platform, am I correct?
Thanks,
Renato
Hmm… the only Corona feature (that I know of) that uses fragments is facebook. Does your app use facebook?
My guess is that this crash happens when the back key is pressed just before a facebook dialog has been displayed. I’ll add this to our “to be investigated” list. So, I’m thinking that it’s not device specific. It’s likely a race condition when pressing the back key while the dialog is being displayed or closed. If you can figure out how to reproduce this issue on your end, then that would help expedite this matter. Thanks for reporting this.
Yes, the app used to have facebook, but we removed it. So, it should not be a problem anymore for us 
Thanks Joshua.