Fix: Upgrade to Expo SDK 46 #426
Merged
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
This reverts commit 148ec9f.
justinpchang
changed the title
This was referenced Mar 24, 2023
|
Addresses #424 (comment) |
nfloersch
approved these changes
Mar 28, 2023
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.
Current release is no longer supported by ExpoGo. I am stepping through each release and upgrading the app and checking for breaking changes until we get to the latest version. Expo only supports 6 months of backwards compatibility with ExpoGo, so latest version will buy us some time and give us the latest tools. I've documented breaking changes and deprecations with each progressive version.
Current version: 43.0.0
expo-app-loaderdeprecated, replicated component locallyexpo-cli)Attempts to upgrade past Expo 46 got really complicated. Will leave that for next year once 46 is dropped from Expo Go support.
@nfloersch Can you please check this branch to make sure things still generally work? I'm not familiar enough with all the functionality to test it properly.