Android 4.4.2 Native method not found: com.mesibo.api.JNIAPI.set_accesstoken
Trying to run the app on Android 4.4.2 throws this error:
E/AndroidRuntime: FATAL EXCEPTION: main Process: com.myapp.testing, PID: 10709 java.lang.UnsatisfiedLinkError: Native method not found: com.mesibo.api.JNIAPI.set_accesstoken:(Ljava/lang/String;)I at com.mesibo.api.JNIAPI.set_accesstoken(Native Method) at com.mesibo.api.Mesibo.setAccessToken(Unknown Source) at com.myapp.testing.Activities.Profile.ChatActivity.startMesibo(Unknown Source) at com.myapp.testing.Activities.Profile.ChatActivity.c(Unknown Source) at com.myapp.testing.Activities.Profile.ChatActivity$2.onResponse(Unknown Source) at retrofit2.ExecutorCallAdapterFactory$ExecutorCallbackCall$1$1.run(Unknown Source) at android.os.Handler.handleCallback(Handler.java:733) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:136) at android.app.ActivityThread.main(ActivityThread.java:5017) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595) at dalvik.system.NativeStart.main(Native Method)
Also: No JNI_OnLoad found in /data/app-lib/com.myapp.testing-1/libcpucheck.so 0xacf8c510, skipping init Trying to load lib /data/app-lib/com.myapp.testing-1/libmesibo.so 0xacf8c510 E/dalvikvm: dlopen("/data/app-lib/com.myapp.testing-1/libmesibo.so") failed: dlopen failed: cannot locate symbol "srand" referenced by "libmesibo.so"...
Kevin, update to latest API 1.0.78 and let us know it resolves it for API level 19
Thanks, I updated to 1.0.78 and still throws that error, and now also this one:
E/AndroidRuntime: FATAL EXCEPTION: main Process: com.myapp.testing, PID: 2197 java.lang.UnsatisfiedLinkError: Native method not found: com.mesibo.api.JNIAPI.get_connectionstatus:()I
Maybe I need an extra configuration for API level 19 to include the native methods?
Kevin. update to latest API 1.0.79 and let us know it resolves it for API level 19
Now seems to works fine on API 19 and above, no errors yet.
i have the same issue with flutter How can i update to the latest API ?