Expo Go on Android fails when EAS Update enabled

Summary

I can’t open projects via Expo Go on Android (2.24.3) if the project has EAS update configured. This affects SDK44 and SDK45.

The behaviour I see in Expo Go is “New update available, downloading…” and it doesn’t progress.

I am highly confident the issue is with Expo Go on Android, because: (1) The problem doesn’t occur on iOS. (2) With a previous version of the Expo app on Android (but the same app checkout from my git repo) I didn’t get the problem.

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": "~45.0.0",
"expo-updates": "~0.13.1",

Environment

expo-env-info 1.0.3 environment info: System: OS: macOS 12.3.1 Shell: 5.8 - /bin/zsh Binaries: Node: 16.15.0 - /opt/homebrew/bin/node Yarn: 1.22.18 - /opt/homebrew/bin/yarn npm: 8.5.5 - /opt/homebrew/bin/npm Managers: CocoaPods: 1.11.3 - /opt/homebrew/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5 Android SDK: API Levels: 30, 31, 32 Build Tools: 29.0.3, 30.0.3, 32.0.0 System Images: android-32 | Google APIs ARM 64 v8a IDEs: Android Studio: 2021.1 AI-211.7628.21.2111.8092744 Xcode: 13.3.1/13E500a - /usr/bin/xcodebuild npmPackages: expo: ~45.0.0 => 45.0.3 react: 17.0.2 => 17.0.2 react-dom: 17.0.2 => 17.0.2 react-native: 0.68.2 => 0.68.2 react-native-web: 0.17.7 => 0.17.7 npmGlobalPackages: expo-cli: 5.4.3 Expo Workflow: managed

Reproducible demo

https://github.com/GregAtFramework/eas-update-breaks-expo-go-on-android/commits/main

Stacktrace (if a crash is involved)

No response

[wschurman]

Thanks for the report! This should be fixed in the most recent version of Expo Go for Android that was released today.

[baronchng]

@RGDEV2022

1. You can remove runtimeVersion field first, then run expo start once.
2. Try to open your app again with Expo GO. Your android app should run now.
3. After it’s fixed, you can reinsert the runtimeVersion field if you still need it and it will work fine on all future expo start.