expo app crushes in production. expo-updates is involved
See original GitHub issue🐛 Bug Report
Summary of Issue (just a few sentences)
After adding expo-updates
to my bare workflow the build fails in production.
Environment - output of expo diagnostics
& the platform(s) you’re targeting
Expo CLI 3.21.7 environment info: System: OS: macOS 10.15.5 Shell: 5.7.1 - /bin/zsh Binaries: Node: 10.13.0 - /usr/local/bin/node Yarn: 1.22.4 - /usr/local/bin/yarn npm: 6.14.4 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman IDEs: Android Studio: 4.0 AI-193.6911.18.40.6514223 Xcode: 11.4/11E146 - /usr/bin/xcodebuild npmPackages: expo: ^37.0.12 => 37.0.12 react: 16.9.0 => 16.9.0 react-dom: 16.9.0 => 16.9.0 react-native: 0.61.4 => 0.61.4 react-native-web: ^0.11.7 => 0.11.7 npmGlobalPackages: expo-cli: 3.18.6
Reproducible Demo
It’s hard to share my code, sorry. This is my stack-trace from production:
I’ve completed all steps from all over the places.
- run expo publish
- update
app.json
- followed
README
instruction fromexpo-updates
page
But still, the build somehow misses the valid app.manifest file.
Sorry for not being more helpful. But help me 😃
Expected Behavior vs Actual Behavior
The app crushes.
Issue Analytics
- State:
- Created 3 years ago
- Comments:31 (10 by maintainers)
Hey @RohovDmytro - sorry this is causing you so much trouble! 😞 Are you able to access the debug logs for your device via
adb logcat
? If so, could you try runningadb logcat | grep "EmbeddedLoader"
, launch the app and paste the output here? That will hopefully give us some more information to work with.it is not. please create a new issue and provide a https://stackoverflow.com/help/mcve and we’d be happy to help! this issue is closed, and so it’s best to create a new issue since what you are facing appears to be different. in general it’s best to avoid commenting on closed issues