java.lang.ExceptionInInitializerError
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1319)
at android.app.Instrumentation.newActivity(Instrumentation.java:1055)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2103)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2236)
at android.app.ActivityThread.access$600(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1238)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5099)
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:803)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:570)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load gideros from loader dalvik.system.PathClassLoader[dexPath=/data/app/com.debia.sostavslova-1.apk,libraryPath=/data/app-lib/com.debia.sostavslova-1]: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:365)
at java.lang.System.loadLibrary(System.java:535)
at com.giderosmobile.android.sostavslovoActivity.(sostavslovoActivity.java:31)
Comments
I have that crash in many apps. I think that it is a reason why mine users have a black screen on application start.
But what we decided to do, is to include some internal error/crash reporting to our own server for fixing purposes, which would allow us to gather anonymous information about device, etc.
Later on we can develop it to something more, displaying error reports also to premium users, for example
I will include it in the labs, once the first version is ready
And yes I think Lua errors are not completely reported, due to how Lua is handled internally, and we are reworking this mechanism so that Lua errors would also cause the proper crashes.
actually all, flurry crashlytics and GiderosReporting report more errors that are provided in Developer console. Because in developer console user actually need to submit the error report. While others simply send it.
Problem with flurry is, that it actually provide too little information about crashes.
I have not used Crashlytics, but lots of folks on the forum are praising it and
As GiderosReporting is still under development, I would probably suggest trying out Crashlytics first