Fix winback tests on iOS 14 & API Tester #4453
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
|
@RCGitBot please test |
|
@RCGitBot please test |
|
@RCGitBot please test |
fire-at-will
changed the title
|
@RCGitBot please test |
vegaro
approved these changes
Nov 7, 2024
|
The |
Closed
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.
This PR addresses a few issues with some tests that aren't normally covered by the
build-testworkflow.Specifically, it addresses two issues:
fulfillment()wasn't introduced until Xcode 13/Swift 5.5/iOS 15. This PR removes the affected tests from compilation on Swift compiler versions <6.0. This won't affect our test coverage of the win-backs feature since win-backs aren't available on iOS versions below 18.