Hello, recently we updated the engine to the version 2019.1f8 to support .aab and 64-bit app bundle.
We released to 50% of our people to test it and actually we did receive a looooooot of crashes since the new update.
Here is a stack trace:
at com.unity3d.player.UnityPlayer.nativeRestartActivityIndicator (Native Method)
at com.unity3d.player.UnityPlayer.resume (Unknown Source:23)
at com.unity3d.player.UnityPlayerActivity.onResume (Unknown Source:5)
at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1412)
at android.app.Activity.performResume (Activity.java:7300)
at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3814)
at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3854)
at android.app.servertransaction.ResumeActivityItem.execute (ResumeActivityItem.java:51)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:145)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:70)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1816)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:193)
at android.app.ActivityThread.main (ActivityThread.java:6718)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)
Please help we really focus on our vitals and this is our blocker to use 2019.
Is it caused by the new Notifications package? If yes, we can remove it until it will be an official release, and be back to our own ones.