expo: Regression: Blank screen display when Updates.reloadAsync() instead of splash screen
Summary
Blank screen display when Updates.reloadAsync() instead of splash screen
Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!
managed
What platform(s) does this occur on?
Android, iOS
SDK Version (managed workflow only)
39
Environment
Expo CLI 4.1.6 environment info: System: OS: macOS 10.15.7 Shell: 5.7.1 - /bin/zsh Binaries: Node: 14.4.0 - /usr/local/bin/node Yarn: 1.22.4 - /usr/local/bin/yarn npm: 6.14.8 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /Users/dev/.rbenv/shims/pod SDKs: iOS SDK: Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0 Android SDK: API Levels: 30 Build Tools: 30.0.1 System Images: android-30 | Google Play Intel x86 Atom IDEs: Android Studio: 4.0 AI-193.6911.18.40.6626763 Xcode: 12.0/12A7209 - /usr/bin/xcodebuild npmPackages: expo: ^39.0.0 => 39.0.5 react: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz => 0.63.2 react-navigation: ^4.4.3 => 4.4.3 npmGlobalPackages: expo-cli: 4.1.6 Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
Happens in any project.
We just udpated from SDK 37 to SDK 39.
We now noticed that on SDK 37, when we invoked Updates.reloadAsync(), the user would be immediately shown the app’s splash screen while the app reloaded.
Now, they are shown an undesired white screen while the app reloads.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 20 (5 by maintainers)
Just updated to SDK 41, issue persists.
Hey guys, especially those running SDK 43, 44, or 45 (after the move to expo modules), I made a PR which I think fixes the issue so that the splash screen shows when you do expo-updates reloadAsync. If you’re able to add it as a patch to your project right away, go for it https://github.com/expo/expo/pull/17592
Any update on this? Seeing it on 43 and 44
This seems to be the case w/ SDK 42 also. 😕 With 43 around the corner hopefully it has the magic ?
Looks like this is also being reported on #13017