Crashing on Startup Android 10 Standalone

  1. SDK Version: 37
  2. Platforms(Android/iOS/web/all): Standalone Android

Hi everyone,

I am having an issue with a particular user of the app. She downloaded the apk from the Google Playstore and opens the app. She sees a white screen then the app crashes before the image on the splash screen appears. She is using a Blu G90 PRO, Android 10 (SDK 29). I haven’t had other reports of crashes.

The crash details I get from Google Play Console are as follows:

Type
java.lang.RuntimeException
java.lang.RuntimeException:
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3326)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3465)
at android.app.servertransaction.LaunchActivityItem.execute (LaunchActivityItem.java:83)
at android.app.servertransaction.TransactionExecutor.executeCallbacks (TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2069)
at android.os.Handler.dispatchMessage (Handler.java:107)
at android.os.Looper.loop (Looper.java:214)
at android.app.ActivityThread.main (ActivityThread.java:7417)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:492)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:980)
Caused by: java.lang.NullPointerException:
at android.os.Parcel.createException (Parcel.java:2077)
at android.os.Parcel.readException (Parcel.java:2039)
at android.os.Parcel.readException (Parcel.java:1987)
at android.app.IAppTask$Stub$Proxy.moveToFront (IAppTask.java:253)
at android.app.ActivityManager$AppTask.moveToFront (ActivityManager.java:4281)
at host.exp.exponent.q.l.a (Kernel.java:89)
at host.exp.exponent.q.l.a (Kernel.java:16)
at host.exp.exponent.q.l.a (Kernel.java:53)
at host.exp.exponent.q.l.a (Kernel.java:47)
at host.exp.exponent.q.l.a (Kernel.java:46)
at host.exp.exponent.q.l.a (Kernel.java:45)
at host.exp.exponent.experience.g.onCreate (DetachActivity.java:5)
at android.app.Activity.performCreate (Activity.java:7817)
at android.app.Activity.performCreate (Activity.java:7806)
at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1306)
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:3301)
Caused by: android.os.RemoteException:
at com.android.server.wm.ActivityStarter.shouldAbortBackgroundActivityStart (ActivityStarter.java:1131)
at com.android.server.wm.AppTaskImpl.moveToFront (AppTaskImpl.java:119)
at android.app.IAppTask$Stub.onTransact (IAppTask.java:135)
at android.os.Binder.execTransactInternal (Binder.java:1021)
at android.os.Binder.execTransact (Binder.java:994)

We have sentry running on the app but I haven’t received any associated logs for the crash. It seems that according to the documentation I might not receive errors from the native code.

Anyone run into a similar bug or knows a good way to debug this? I don’t have access to the user’s phone.

Any help is greatly appreciated.

Thanks!

1 Like
  1. SDK Version: 36
  2. Platforms(Android): Standalone Android
  3. Device: Gigaset GX290, Android 10 (SDK 29)
  4. Bundle-Type: .aab

Hi there, any news on this issue? We have the same problem with one user. Also no reports in sentry etc.

1 Like

Based on the middle part of the stack trace it looks to me like there could be some Expo code that needs to handle this android.os.RemoteException. The answers to this Stack Overflow question seem to explain what types of errors can cause an android.os.RemoteException.

Since you’re both running slightly older SDK versions it’s possible that upgrading to SDK 39 would fix this, but I haven’t found anything to indicate that this issue has been fixed.

I don’t see any Expo issues that mention RemoteException. If you don’t get an answer here I would create a new issue with the details from this thread, including the stack trace.

1 Like

@bhhcappdev and @aidminutes
I think SDK 38 and 39 probably have better support for Android 10, so it is probably worth upgrading.
Apparently the fact that host.exp.exponent.q.l.a appears in the stack trace doesn’t mean too much.

1 Like

Thank you! We are looking into upgrading to the latest sdk and hopefully that resolves the issue for the user.