java.lang.ExceptionInInitializerError -- is this GPGS related error?

Solar2D Android
#1

This error has been reported by the user of my app on Google Play.  I’m not sure, but could it be Google Play Game Services related error?  Can this be fixed?  The APK was built with Corona 1203.

Naomi

java.lang.UnsatisfiedLinkError

in java.lang.Runtime.loadLibrary

java.lang.ExceptionInInitializerError
at com.ansca.corona.CoronaActivity.onCreate(CoronaActivity.java:115)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1622)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1674)
at android.app.ActivityThread.access$1500(ActivityThread.java:117)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:130)
at android.app.ActivityThread.main(ActivityThread.java:3735)
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:904)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:662)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.ExceptionInInitializerError
at com.ansca.corona.CoronaEnvironment.setLuaErrorHandler(CoronaEnvironment.java:373)
at com.ansca.corona.CoronaEnvironment.<clinit>(CoronaEnvironment.java:41)
… 14 more
Caused by: java.lang.UnsatisfiedLinkError: Couldn’t load lua: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:429)
at java.lang.System.loadLibrary(System.java:554)
at com.ansca.corona.JavaToNativeShim.<clinit>(JavaToNativeShim.java:108)
… 16 more

#2

I have had reports of this error as well with a 1203 build. I haven’t had this error before. I don’t get it when I test on my own device though. Does the recent 1210 build fix this? I can’t tell since I don’t get this error and I am only hearing about it from some users.

#3

I have had reports of this error as well with a 1203 build. I haven’t had this error before. I don’t get it when I test on my own device though. Does the recent 1210 build fix this? I can’t tell since I don’t get this error and I am only hearing about it from some users.

#4

hi Noemi

I have this error , do you know why already??

I´m working with build 1202

regards

#5

@antonio.capel, I don’t know the cause of this error.  That said, I haven’t seen this error for a while (even though I have not changed the code.)  I mean, I haven’t seen it lately.  I also haven’t seen any user reporting it.  I don’t know if it made any difference but my latest version of my app was built with daily build 1257.

Naomi 

#6

thank you very much for your answer Noemi!! you are very kind.

I´ll  update my version

Corona should pay you 

regards

#7

hi Noemi

I have this error , do you know why already??

I´m working with build 1202

regards

#8

@antonio.capel, I don’t know the cause of this error.  That said, I haven’t seen this error for a while (even though I have not changed the code.)  I mean, I haven’t seen it lately.  I also haven’t seen any user reporting it.  I don’t know if it made any difference but my latest version of my app was built with daily build 1257.

Naomi 

#9

thank you very much for your answer Noemi!! you are very kind.

I´ll  update my version

Corona should pay you 

regards

#10

I am seeing that same error in my last game update made using build 2.100. 

Any help would be appreciated.

#11

I am seeing that same error in my last game update made using build 2.100. 

Any help would be appreciated.