Future proof for different objectVersion (include objectVersion 70)#1020
Open
kronenthaler wants to merge 1 commit intoCocoaPods:masterfrom
Open
Future proof for different objectVersion (include objectVersion 70)#1020kronenthaler wants to merge 1 commit intoCocoaPods:masterfrom
kronenthaler wants to merge 1 commit intoCocoaPods:masterfrom
Conversation
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.
the xcodeproj format includes a version value that can help with some parsing options, however, Xcode can use different values for the same version of Xcode (e.g with Xcode 16.2, selecting project format 15.3 will give you an
objectVersion: 70) whereas xcodeproj assumes that Xcode 15.3 is 63.This
objectVersionis used as a key to populate another value which is mostly for human consumption (compatibility_version) However, neither Xcode, nor other tools i have used rely on it for anything.The problem arises when an "unknown" version is presented to xcodeproj for parsing. Not always is possible to edit it in xcode prior running
pod installor parsing the project. For example, if the project is generated with xcodegen this number is fixed and always regenerated.This PR aims to right that wrong. Basically, consuming the value from the project, and only populating the
compatibility_versionif it's known, but doesn't stop the project from carry on working, making it more future proof.