Use purchase(confirmIn:) when possible #4606
Closed
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 |
|
@RCGitBot please test |
|
@RCGitBot please test |
|
Closing this PR since the underlying StoreKit bug is reproducible with |
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.
Motivation
We've received some reports showing failures on iOS 18.2+ where StoreKit can't find the scene to present the purchase sheet over. According to some reports, using
purchase(confirmIn:options:)can resolve this issue.Description
This PR modifies the SDK to use
purchase(confirmIn:options:)when it can fetch the current scene and when the API is availableTODO
Test, test, test!