Revert "feat(eas-cli): expose expo export dev flag as an option in eas update (#2050)" #2214
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
This reverts commit 8751a28.
The reason we're reverting this is that it is causing some confusion around whether dev bundles work with EAS update. The answer is that they probably shouldn't, or at least aren't officially supported.
Instead, to address the original concern in #2050 (accessing the dev menu), we'll address that issue in a more targeted manner: by making accessing the dev menu even in places when
__DEV__
isn't set.Alternatively, one could theoretically do the export step manually during an
eas update
by running thenpx expo export
command manually and then runningeas update --skip-bundler
.Closes ENG-11290.
How
Revert.
Test Plan
CI