Skip to content

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

Open
Open
Implement in-app activation and remote watch based passes for IOS#84
Labels
enhancementNew feature or request

Description

@ShpetimA
ShpetimA
opened on Jun 4, 2026

Hi guys,
I have a fork of this library where I have implemented the watch based filtering logic for inapp-provisioning and added endpoint for in-app activation flows.
At my current company we are going through the verification process for apple, these were needed to pass apple requirements from their test cases.
If there is interest I could cleanup the code and create a pr to implement these features.

Activity

  1. JakubKorytko commented on Oct 1, 2026

    @JakubKorytko
    JakubKorytko
    on Oct 1, 2026
    Member

    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 request
    on Oct 1, 2026

  3. Brunonascdev commented on Oct 12, 2026

    @Brunonascdev
    Brunonascdev
    on Oct 12, 2026
    Contributor

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

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

  4. Brunonascdev commented on Oct 29, 2026

    @Brunonascdev
    Brunonascdev
    on Oct 29, 2026
    Contributor

    We can probably close this one @JakubKorytko

  5. JakubKorytko commented on Oct 29, 2026

    @JakubKorytko
    JakubKorytko
    on Oct 29, 2026
    Member

    Thanks @Brunonascdev! I'd keep this open for now, two things left:

    1. The new APIs (canAddCardToAppleWallet, listAppleWalletPasses, activateAppleWalletPass) aren't in the example app yet.
    2. @ShpetimA, since these are ports of your fork, could you check if the released versions work for you? The Watch-aware provisioning is in 0.2.23 (feat: pass optional primaryAccountIdentifier to Apple Wallet #91), listing and activating passes, including on a paired Watch, in 0.2.24 (List Apple Wallet passes and activate them in-app #96).

  6. ShpetimA commented on Oct 29, 2026

    @ShpetimA
    ShpetimA
    on Oct 29, 2026
    Author

    I'll check it out when I have some time, and report back since most of the testing can be done in production enviorment with apple, will take me some time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions