Got following stacktrace from Android Vitals:
java.lang.Error: FATAL EXCEPTION [main]
Unity version : 5.6.2f1
Device model : samsung SM-G955F
Device fingerprint: samsung/dream2ltexx/dream2lte:8.0.0/*****/***********B7:user/release-keys
Caused by
at bitter.jnibridge.JNIBridge.invoke (Native Method)
at bitter.jnibridge.JNIBridge$a.invoke (Unknown Source:20)
at java.lang.reflect.Proxy.invoke (Proxy.java:913)
at $Proxy1.onBindingDied (Unknown Source)
at android.app.LoadedApk$ServiceDispatcher.doConnected (LoadedApk.java:1652)
at android.app.LoadedApk$ServiceDispatcher$RunConnection.run (LoadedApk.java:1685)
at android.os.Handler.handleCallback (Handler.java:789)
at android.os.Handler.dispatchMessage (Handler.java:98)
at android.os.Looper.loop (Looper.java:164)
at android.app.ActivityThread.main (ActivityThread.java:6938)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:327)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1374)
Have no clue. Any help or explanation will be welcome.
We have managed to reproduce the bug on Android 8.0 with Unity 2017.2.1.
Upgrade to Unity 2017.4.7 LTS has fixed the issue.
We were seeing the same error out of a large portion of our player base. We were able to contact Unity and get some insight into the error.
From Unity Enterprise Support:
We have decided to try and upgrade our Unity Version from 5.6.4f1 into the recommended 2017 versions. Sounds like it should resolve our issues.
Today for our project in Android Vitals for users on Android 8.0 and 8.1 began to display the same failure. We use Unity 2017.1.3 Maybe it does not depend on the version of Unity. I found some correlation of the occurrence of such a failure with the release of updates for Google Play Market.
UPDATE: We were able to reproduce this error on our Android 8.1 device:
Given the peculiarity of this error to appear unexpectedly and massively, and then also unexpectedly disappear completely without making changes to the application, we concluded that the system service stops forcibly when the background of the Google Play Market is updated for users with auto-update enabled and connecting to the WiFi network during use our application and then try to access the data or conduct an operation with IAP in the Google Play store.