Repository navigation
feat: pass optional primaryAccountIdentifier to Apple Wallet #91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Brunonascdev
wants to merge
6
commits into
Expensify:main
Choose a base branch
from
Brunonascdev:feat/ios-primary-account-identifier
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+180
−18
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
fcc4cdd
feat: pass optional primaryAccountIdentifier to Apple Wallet
Brunonascdev 794afd5
Merge origin/main into feat/ios-primary-account-identifier
Brunonascdev 25154d3
fix: reject when a card is already on every Apple device
Brunonascdev 078464e
feat: tell apps which Apple device can still take the card
Brunonascdev 32556d9
chore: drop field comments that the rest of the types do not use
Brunonascdev 934dc35
fix: match Apple Watch passes more reliably
Brunonascdev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this one: what happens when the pass with this id is already on every device (iPhone and Watch)? If PassKit has nowhere to add it,
PKAddPaymentPassViewController(...)might return nil and the user gets "InApp enrollment controller configuration fails", which is confusing. Did you get a chance to check that case? If it is a real problem,PKPassLibrary().canAddSecureElementPass(primaryAccountIdentifier:)could be used to give a clearer error.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked this. When
primaryAccountIdentifieris set andPKPassLibrary.canAddSecureElementPass(primaryAccountIdentifier:)is false, we now reject before creating the controller, with "This card has already been added to all available devices." The same check is exposed ascanAddCardToAppleWallet, so the app can hide the Add button before the user taps it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow-up: this check is now advisory.
canAddSecureElementPasshas been reported to return false after a card is added to the iPhone even when a paired Watch can still take it (https://developer.apple.com/forums/thread/113967), so a false result no longer blocks provisioning. We only use it to choose the error message whenPKAddPaymentPassViewControlleritself returns nil.