expo: Stuck on "Checking for new update"
Summary
JS-bundle produced by expo-build hangs on “checking for new update”. Running expo start --dev-client in the same state works and loading the bundle from there with the same dev-client works fine.
Managed or bare workflow? If you have made manual changes inside of the ios/ or android/ directories in your project, the answer is bare!
managed
What platform(s) does this occur on?
Android
Package versions
"expo-dev-client": "~0.6.3",
"expo": "~43.0.3",
"expo-updates": "~0.10.15",
Dev-client generated by eas build --profile development --platform android
from: eas-cli/0.37.0 darwin-x64 node-v14.18.0
Environment
Expo CLI 4.13.0 environment info: System: OS: macOS 11.5.2 Shell: 5.8 - /bin/zsh Binaries: Node: 14.18.0 - ~/.nvm/versions/node/v14.18.0/bin/node Yarn: 1.22.15 - ~/.nvm/versions/node/v14.18.0/bin/yarn npm: 6.14.15 - ~/.nvm/versions/node/v14.18.0/bin/npm Watchman: 2021.10.18.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.2 - /Users/prototyp/.rbenv/shims/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 18, 21, 22, 23, 24, 25, 28, 29, 30 Build Tools: 20.0.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 24.0.0, 24.0.1, 24.0.2, 24.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 27.0.0, 27.0.1, 28.0.3, 29.0.2, 30.0.2 System Images: a…google_apis | Google APIs Intel x86 Atom Sys…, a…-tv | Android TV ARM EABI v7a System…, a… | Android TV Intel x86 Atom Syst…, a…ear | Android Wear ARM EABI v7a Syst…, a…ndroid-wear | Android Wear Intel x86 Atom Sy…, a…-23 | Intel x86 Atom, a… | Intel x86 Atom_64, a…pis | Google APIs ARM EABI v7a Syste…, a…google_apis | Google APIs Intel x86 Atom Sys…, a…gle_apis | Google APIs Intel x86 Atom_64 …, a… | Android TV Intel x86 Atom Syst…, a…fault | ARM 64 v8a, a…ult | ARM EABI v7a, a…-24 | Intel x86 Atom, a… | Intel x86 Atom_64, a…_apis | Google APIs ARM 64 v8a System …, a…pis | Google APIs ARM EABI v7a Syste…, a…google_apis | Google APIs Intel x86 Atom Sys…, a…gle_apis | Google APIs Intel x86 Atom_64 …, a…s_playstore | Google Play Intel x86 Atom Sys…, a… | Android TV Intel x86 Atom Syst…, a…ear | Android Wear ARM EABI v7a Syst…, a…ndroid-wear | Android Wear Intel x86 Atom Sy…, a…_apis | Google APIs ARM 64 v8a System …, a…pis | Google APIs ARM EABI v7a Syste…, a…google_apis | Google APIs Intel x86 Atom Sys…, a…gle_apis | Google APIs Intel x86 Atom_64 …, a…s_playstore | Google Play Intel x86 Atom Sys…, a…google_apis | Google APIs Intel x86 Atom Sys…, a…google_apis | Google APIs Intel x86 Atom Sys…, a…google_apis | Google APIs Intel x86 Atom Sys… IDEs: Android Studio: 2020.3 AI-203.7717.56.2031.7784292 Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild npmPackages: expo: ~43.0.3 => 43.0.3 react: 17.0.1 => 17.0.1 react-dom: 17.0.1 => 17.0.1 react-native: 0.64.3 => 0.64.3 react-native-web: 0.17.1 => 0.17.1 npmGlobalPackages: expo-cli: 4.13.0 Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
- expo init
- Install one native package (I used
react-native-agorawhich requires WebRTC) - Create a custom development client using
eas build - Install .apk on real Android device (Samsung Galaxy S20+)
- Run
expo start --dev-clientand make sure the app works and is able to run. - Run
expo publish - Scan QR-code and open on same Android device
- First time I do this, my app is stuck on the splash screen, showing the text at the bottom: “New update available, downloading”
- All subsequent times I try opening the published URL, the app is suck on same splash screen, showing “Checking for new update”
Stacktrace (if a crash is involved)
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 24 (11 by maintainers)
I have this same error in Expo SDK 44.
Th expo publish works “fine” but when Expo Go launch the app with the legend in the bottom: “New update available, downloading”. Freeze in this point 😦
I experienced same error regardless i m using qr code or link, the app works on ios but not on android
Unresponsive:
@davidcort - check out https://github.com/expo/fyi/blob/main/splash-screen-hanging.md
you could create a development build for an expo-go-like experience but with any native module 😃 https://docs.expo.dev/development/introduction/
Ok so update on my part. My problem was absent “scheme” in app.json (despite it isn’t used in expo app but I am using expo-linking lib). I went back and forth to confirm this and it is reproducible. (https://docs.expo.dev/guides/linking/#in-a-standalone-app) Problem is that I read many people have this issue and “cures” it in many different ways so the problem may have different origins. There is no way of diagnosing this because in development everything seems fine then you go publish and surprise surprise it doesn’t work and give nothing which tells you what’s wrong.
i’m going to reopen this issue for now because it was created before we updated the issue template to always ask for a reproducible example rather than just steps. also shared with the dev client team