Post

Replies

Boosts

Views

Activity

Reply to Apple Wallet Issuer Extension
I managed to make it work. There are few key points to follow: Make sure that you have correct values in info.plist in Non-UI and UI extension (NSExtensionPointIdentifier, NSExtensionPrincipalClass) Make sure you have com.apple.developer.payment-pass-provisioning entitlement for your app and both extensions Make sure that your function func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) inside Non-UI extension executes in under 100ms. The extension is not displayed to the user in Wallet if this criteria is not met. Make sure that in your function func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) the object PKIssuerProvisioningExtensionStatus has remotePassEntriesAvailable or passEntriesAvailable set to true (if there are no cards to add to the wallet, your app won't be displayed). For the purpose of trying it out inside your Non-UI extension just implement status function like that: override func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) { let status = PKIssuerProvisioningExtensionStatus() status.remotePassEntriesAvailable = true status.passEntriesAvailable = true status.requiresAuthentication = false completion(status) } I hope it helps :)
Feb ’24
Reply to Apple Wallet Issuer Extension
Hey, did you managed to solve it? I have also created non-ui and ui extension, but i am stuck where the app is not getting displayed in the apple wallet. Is there any tutorial that I could follow?
Replies
Boosts
Views
Activity
Jan ’24
Reply to Watch connectivity inside Apple Wallet Issuer Extension
I also noticed, when adding a card from that extension the function remotePassEntries is never called. I can confirm that iWatch is connected to the iPhone and the param remotePassEntriesAvailable is set to true when function status is called. In which case is the function remotePassEntries called?
Replies
Boosts
Views
Activity
Feb ’24
Reply to Apple Wallet Issuer Extension
I managed to make it work. There are few key points to follow: Make sure that you have correct values in info.plist in Non-UI and UI extension (NSExtensionPointIdentifier, NSExtensionPrincipalClass) Make sure you have com.apple.developer.payment-pass-provisioning entitlement for your app and both extensions Make sure that your function func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) inside Non-UI extension executes in under 100ms. The extension is not displayed to the user in Wallet if this criteria is not met. Make sure that in your function func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) the object PKIssuerProvisioningExtensionStatus has remotePassEntriesAvailable or passEntriesAvailable set to true (if there are no cards to add to the wallet, your app won't be displayed). For the purpose of trying it out inside your Non-UI extension just implement status function like that: override func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) { let status = PKIssuerProvisioningExtensionStatus() status.remotePassEntriesAvailable = true status.passEntriesAvailable = true status.requiresAuthentication = false completion(status) } I hope it helps :)
Replies
Boosts
Views
Activity
Feb ’24
Reply to Watch connectivity inside Apple Wallet Issuer Extension
I found the answer to this as remotePassEntries is called only when the user is trying to add the cards to the watch via "Watch" app
Replies
Boosts
Views
Activity
Mar ’24