Google feature our game Compulsive today and now we have a ton of crashes. Can you help figure out whatās wrong?
Stack:
java.lang.ExceptionInInitializerError
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1409)
at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1561)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1663)
at android.app.ActivityThread.access$1500(ActivityThread.java:117)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:931)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3683)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:864)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:622)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load compulsive: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:429)
at java.lang.System.loadLibrary(System.java:554)
at com.tmsoft.compulsive.Compulsive.(Compulsive.java:30)
... 15 more
I havenāt checked every device from your list, but it seems that all of them use processors based on ARMv6 architecture. So building for armeabi should work fine (and adding armeabi-v7a definitely wonāt help).
Are you sure your app does not use any ARMv7 (or some other architecture) specific code?
I canāt imagine there being anything ARMv7 specific in the code. Itās pretty much stock cocos2dx 2.2 with libraries like mopub, facebook, google play services, etc. I might just have to buy an ARM6 device and see what is going on. Iāve read in other places that it could also be the download from the play store getting corrupted causing the findlibrary call to fail. It seems like I have the exact same problem as Tobias S. It sure would be great to get an answer on thisā¦ Does anyone out there have an ARM6 device they could try out my game? https://play.google.com/store/apps/details?id=com.tmsoft.compulsive
I received my Samsung Ace phone which has a bunch of crashes in the dev console. Downloaded my game from play store and it ran without issue. No crashes. So itās not the device from what I can tell. I think this is a software delivery issue from the play store.
Well, thatās weird. I havenāt heard about delivery issues of Play Store.
It would be great if you could find some advanced user who could send you the ācorruptedā (if it is) apk he/she downloaded from Play Store for investigation.
I spoke with the cocos2dx developers at GDC on this issue and they believe these older devices just run out of memory and so the call to load library fails.
I would suggest you to google up problematic devices that crashes in most of the games due to poor
implementation of GPU drivers and exclude them in developer console. BTW most of devices are Samsung with this issue, there are others but these are most problematic.
Here is what should you exclude, google for more.
short list:
All Galaxy ACE series
All Galaxy Y series
All Galaxy Pocket
