$ expo diagnostics Expo CLI 3.2.3 environment info: System: OS: macOS 10.14.6 Shell: 5.3 - /bin/zsh Binaries: Node: 12.10.0 - /usr/local/bin/node Yarn: 1.16.0 - /usr/local/bin/yarn npm: 6.12.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 3.5 AI-191.8026.42.35.5791312 Xcode: 11.1/11A1027 - /usr/bin/xcodebuild npmPackages: expo: 35.0.0 => 35.0.0 react: 16.8.3 => 16.8.3 react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8 react-navigation: 4.0.7 => 4.0.7 npmGlobalPackages: expo-cli: 3.2.3
Since upgrading to
email@example.com, we’ve been seeing errors running
expo start -c. When we first ran
expo start -c, it worked fine. After that first time, we’ve been seeing the same behavior:
- We run
expo start -c
- The Metro Bundler page opens, and shows:
- After 10 seconds or so, the Metro Bundler page turns completely black, and in our terminal we see:
Could not get status from Metro bundler. Request failed with status code 404 Connecting to Metro bundler failed.
- We try running
expo start -cagain, and it works fine.
At first, while this was a little annoying, we weren’t too worried about it. But then our first TestFlight user told us that their app is getting stuck on the splash screen. We’re not 100% sure that the two are related. But since our app is working fine on our TestFlight, we’re wondering whether they might be related.
We saw in other threads that the 404 error can happen when your bundle is too large (> 30mb). Our bundle is 10.75mb, so we don’t think that’s the issue.
Any idea what’s causing this?