fix: Push Provisioning issues on iOS due to Apple bugs #1305
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.
Summary
There is some unexpected behavior from Apple we need to account for.
false
, even though the device can add payment passes, so we removed reliance on that method.false
response from canAddSecureElementPass when a paired Watch is still available for provisioning, so we removed reliance on that method.Motivation
Temporarily fix push provisioning flow on iPads and when there is a paired watch, until Apple fixes this in PassKit.
Testing
Testing this takes a while, TODO
Documentation
Select one: