I don’t know if this behavior occurred in any of the SDKs prior to 39 because I never tried running expo start -no-dev -minify in the earlier versions (being unaware of the command expo start -no-dev -minify at that point). That is when I became aware of the issue and when I learned how to run an app locally in Production mode. The “frozen on the splash screen” behavior first surfaced when an app bundle was built and uploaded to the Google Play Store after the SDK upgrades.
The upgrades were done one at a time (36 → 37, 37 → 38, 38 → 39) but all on the same day. The app was originally developed using Expo SDK 36 but when an app bundle was built it would not upload to the Google Play Store which is what triggered upgrading the project to SDK 39. After the animation code was removed from the project then the app ran normally when that command was issued. OS: Linux 5.4 Ubuntu 18.04.5 LTS (Bionic Beaver)Įxpo Workflow: Yes, the “frozen on the splash screen” behavior was reproducible when run locally in production mode using expo start -no-dev -minify. What would cause this behavior? What steps should I take next to debug/resolve this issue? The tester has tried restarting the phone, Force Stop the Google Play app, Clear Data and Clear Cache for Google Play app, uninstall/reinstall the app.
However, once the app is installed on the tester’s phone and the Open button is tapped it gets stuck on the splash screen and will not go any further. Then I ran expo build:android -type app-bundle, allowed the Keystore to be generated automatically and uploaded the app bundle to Google Play Console and made it available for internal testers. I developed an app that works fine in the development environment.
0 kommentar(er)
