Allow users to manually launch updates in Expo Go #226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alanjhughes
approved these changes
Nov 26, 2024
gabrieldonadel
deleted the
@gabrieldonadel/force-expo-go-update-launch
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
When users manually set their
runtimeVersionto something other thanexposdk:x.x.x, there is no way for us to detect if that app is compatible with Expo Go or not, given that, we should allow user to manually launch updates in Expo GoHow
Introduce a new
--force-expo-goflag to launch-update command allowing users to manually specify that their runtime version is compatible with Expo GoTest Plan
Run MenuBar locally