feat: upgrade managedExpo example to Expo SDK 51 #247
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
lukasjhan
changed the title
|
Be advised, I didn't test it in iOS. It may not be working correctly on iOS devices. |
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.
Hi iamport maintainers.
Upgrade Expo SDK to version 51 for compatibility with latest Expo Go app
This PR updates the Expo SDK version from 49 to 51 in the iamport
mangedExpoexample. The previous version in themangedExpoexample was incompatible with the latest Expo Go app. It requires SDK version 51.Changes made:
This update ensures that the example can be run on the most recent version of the Expo Go app, improving accessibility for developers using the latest tools.
Thank you for considering my contribution!