Runtime Version from AndroidManifest truncates tailing zeros making "1.10" into "1.1"
See original GitHub issueSummary
My production app was unable to update via OTA and i found that runtime version has been invalid and update was not applied due invalid runtime version
Managed or bare workflow? If you have ios/
or android/
directories in your project, the answer is bare!
bare
What platform(s) does this occur on?
Android
SDK Version (managed workflow only)
No response
Environment
Expo CLI 3.28.5 environment info: System: OS: macOS 11.2.3 Shell: 5.8 - /bin/zsh Binaries: Node: 15.14.0 - /usr/local/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 7.7.6 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 22, 23, 24, 25, 26, 27, 28, 29, 30 Build Tools: 28.0.3, 29.0.2, 30.0.0 System Images: android-28 | Google APIs Intel x86 Atom IDEs: Xcode: 12.5/12E262 - /usr/bin/xcodebuild npmPackages: expo: 41.0.1 => 41.0.1 react: 17.0.2 => 17.0.2 react-dom: 17.0.2 => 17.0.2 react-native: 0.64.2 => 0.64.2 react-native-web: 0.16.1 => 0.16.1 npmGlobalPackages: expo-cli: 4.3.0 Expo Workflow: bare
Reproducible demo or steps to reproduce from a blank project
Just set expo.modules.updates.EXPO_RUNTIME_VERSION
to 1.10
and try to perform OTA.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top GitHub Comments
In my case i hit it my production app and eventually switched to single-digit version as work-around.
OK. Thanks for letting us know about this!