Update upgrading-expo skill with iOS deployment target#63
Open
eithe wants to merge 1 commit into
Open
Conversation
Expo 55 -> 56 (and potentially the corresponding RN upgrade ) requires a higher minimum target version.
Our app was at 15.1 and required 16.4.
[!] CocoaPods could not find compatible versions for pod "Expo":
In Podfile:
Expo (from `../node_modules/expo`)
Specs satisfying the `Expo (from `../node_modules/expo`)` dependency were found, but they required a higher minimum deployment target.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Upgrading Expo (and potentially the corresponding RN upgrade) often requires a higher minimum target version.
For Expo 55 -> 56, our app was at 15.1 and required 16.4.
This PR updates the upgrading-expo skill to handle this.