Update version detection for --legacy flag due to changes in xcresulttool version number
#9
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.
Xcode 16:
xcresulttool version 23024, format version 3.53 (current)Xcode 26:
xcresulttool version 24051.1, schema version: 0.1.0 (legacy commands format version: 3.53)The regular expression added to determine if the
--legacyparameter is needed only matched on numeric characters for the version, the new version number has a decimal and would result in a null pointer error being thrown when trying to get the version. Updated to optionally support the decimalised version number. If no match is found, assume it's a newer version and assume--legacyis needed in this case as well.This is the trace seen when this issue this PR resolves is hit: