[Android] RunTimeException after upgrading to SDK 40

Expo SDK
1

Please provide the following:

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

Hi, after my recent upgrade to SDK 40 I get errors in Android production app, which were never there before. Since stack traces in android dev console are not easily readable, I was hoping that maybe someone could point me to solution.

Here’s the stack trace:

java.lang.RuntimeException: 
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:4589)
  at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:4621)
  at android.app.servertransaction.ResumeActivityItem.execute (ResumeActivityItem.java:52)
  at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:176)
  at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2198)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:233)
  at android.app.ActivityThread.main (ActivityThread.java:7959)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:631)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:978)
Caused by: java.lang.RuntimeException: 
  at host.exp.exponent.experience.q.E (BaseExperienceActivity.java:7)
  at host.exp.exponent.experience.a.run (Unknown Source:2)
  at android.app.Activity.runOnUiThread (Activity.java:7074)
  at host.exp.exponent.experience.q.D (BaseExperienceActivity.java:2)
  at host.exp.exponent.experience.q.onResume (BaseExperienceActivity.java:5)
  at host.exp.exponent.experience.ExperienceActivity.onResume (ExperienceActivity.java:1)
  at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1571)
  at android.app.Activity.performResume (Activity.java:8141)
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:4579)

This issue seems to occur mostly on Android 11 and Huawei phones, but with current rate (right now there are only 21 occurrences) it can albo be accidental correlation.

I’ll gladly share more informations about my setup if it could help pinpointing the issue.

Thanks in advance!

2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.