Implement in-app activation and remote watch based passes for IOS #84

Activity

1. JakubKorytko commented on Oct 1, 2026

   

   JakubKorytko

   on Oct 1, 2026

   Member

   More actions

   Hey, sorry for the slow reply here! These would be useful additions, they line up with #45 (in-app activation) and #56 (multi-device / Apple Watch provisioning), so a PR is welcome. A few requests to make review easier:

   • Split it into two PRs: Watch/remote pass handling, and in-app activation. The Watch part should build on primaryAccountIdentifier from feat: pass optional primaryAccountIdentifier to Apple Wallet #91, so it'd be great to base it on that once it lands.
   • Document the new APIs in the README and add them to the example app.
   • Since this can't be tested on a simulator, please describe what you tested on device (iPhone + paired Watch).

   Thanks!
2. JakubKorytko

   added

   enhancementNew feature or requestNew feature or request

   on Oct 1, 2026
3. Brunonascdev commented on Oct 12, 2026

   

   Brunonascdev

   on Oct 12, 2026

   More actions

   @ShpetimA I ported some of the changes from your fork into two PRs:

   • feat: pass optional primaryAccountIdentifier to Apple Wallet #91 picks up the Apple Watch pass matching: local passes skip isRemotePass, a last-digits match is used only when exactly one pass matches and the caller passed an id, and canAddSecureElementPass is advisory.
   • List Apple Wallet passes and activate them in-app #96 adds listAppleWalletPasses and activateAppleWalletPass, including activation of a pass on a paired Watch (d122f802, ca6c4044).

   I left out the change that makes primaryAccountIdentifier required, and the separate canAddSecureElementPass method, because #91 already covers provisioning with an optional identifier.

   ❤️React with ❤️2Reacted by Jakub Korytko and Shpetim