expo: [SDKv44][Android] Production mode fails with many imports (failed to load all assets)
Summary
Many imports in App.js crashes the app in Stores. It is only reproducible in Android Emulator, in iOS Emulator is working fine but crashes the app in TestFlight. I think it is something like “timeout” because it always fails in a certain small time regardless of the imports.
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)
44.0.0
Environment
Expo CLI 5.0.3 environment info: System: OS: macOS 12.0.1 Shell: 5.8 - /bin/zsh Binaries: Node: 16.13.1 - /usr/local/bin/node npm: 8.1.2 - /usr/local/bin/npm Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3 Android SDK: API Levels: 30 Build Tools: 30.0.3, 31.0.0 System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom IDEs: Android Studio: 2020.3 AI-203.7717.56.2031.7935034 Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild npmPackages: expo: ~44.0.0 => 44.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 react-navigation: ^4.4.4 => 4.4.4 npmGlobalPackages: eas-cli: 0.43.0 expo-cli: 5.0.3 Expo Workflow: managed
Reproducible demo
Clone https://github.com/jereztech/demo-expo.git, install and expo start --no-dev --minify -c, to reproduce always clear the cache!
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 29 (9 by maintainers)
@esamelson the error sometimes also occurs on iOS using
expo start --no-dev --minify -cin the simulator or Expo Go, the problem is that we can’t reload the app in production on the client devices, so do a build witheas buildcrashes the app and will be rejected by Apple/Google Stores, withexpo buildis working fine. I have followed the documentation indicated by @brentvatne but without success. The app fails with “Failed to load all assets” message without further information.i passed this on to the folks that work on expo-updates, they will investigate
I have the same problem, the worst thing is that it didn’t get solved even if I went back to sdk 43.
same problem with 47
For folks having issues: what do your native iOS (use Mac’s Console.app) and Android (use adb logcat) logs say? There is often an error or log entry tagged with your bundle identifier/application ID that provides info about what went wrong.
hi @philheb this error still persists, I keep sending updates for the Stores with expo:build
An issue with expo-updates on Android that was released with SDK 44 was identified and a fix is in progress – https://github.com/expo/expo/pull/15880, https://github.com/expo/expo/pull/15882.
@cah-caleb-boyd: the report in the first post pertains to Android. I suspect the issue on iOS is unrelated. It looks like a possible misconfiguration given the crash is coming from here https://github.com/expo/expo/blob/e197a05c13ce10c77741183d5aea5e798d9a846b/packages/expo-updates/ios/EXUpdates/EXUpdatesAppController.m#L252 and is about an unknown selector. I recommend a brand new project / more minimal project to reproduce the issue so we can look into it if it still is an issue.