We have a single user who cannot run our ExpoKit 36 app. It shows the splash screen and just stays there.
What I know:
The phone: Samsung Galaxy J2 Pure. This appears to be an Android Go phone running either Android 8.1 or 9. Extremely low-end, probably has only 1 GB of RAM.
There was a crash reported to Play Store Console a few days before we got the help ticket for a Galaxy J2 Pure running Android 9.0. Not a lot of info, but the error from console:
Caused by: java.lang.RuntimeException: at host.exp.exponent.experience.a$b.run (BaseExperienceActivity.java:7) at android.app.Activity.runOnUiThread (Activity.java:6424) at host.exp.exponent.experience.a.k (BaseExperienceActivity.java:2) at host.exp.exponent.experience.a.onResume (BaseExperienceActivity.java:5) at host.exp.exponent.experience.ExperienceActivity.onResume (ExperienceActivity.java:1) at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1416) at android.app.Activity.performResume (Activity.java:7630) at android.app.ActivityThread.performResumeActivity (ActivityThread.java:4054)
So it seems possible that this user had a crash originally and after that the app kept hanging.
We’ve had the user try all the app troubleshooting steps recommended by Samsung (https://www.samsung.com/au/support/mobile-devices/app-crashing/) except the more technical “clear cache partition” option. So, uninstall reinstall, clear data, etc.
We use the default options for OTA updates, so it tries to grab latest with a 30 second timeout.
- Anyone seen anything like this?
- The crash and then the hang has me wondering if something went bad with an OTA update. But I thought clearing app data would reset that. Anything else the user should try?
- Anyone have any trouble with their Expo apps and Android Go (https://www.android.com/versions/go-edition/)? The size of the average Expo app is obviously outside their normal recommendations, but I ran my app in profiler on an AVD with 1 GB RAM and didn’t see any issues.