@Frameworks Engineer I am stuck with the same issue. I did try setting primaryAccountIdentifier to a unique identifier but it did not help. It always lists all the devices. Can you please help?

@omatheus Can you please help me understand how you implemented the below using wallet extensions? How did you fetch the list of cards available for provisioning in Wallet extension? How did you cross-verify which cards are already added to Wallet or not before we show the list in Wallet app? How did you perform app authentication inside Wallet extension to get the encrypted card data from backend? This is because our app uses custom authentication framework with passcode

@foxulee Yes! It turns out it was an issue with the way the encryption was done. Fixing that worked for us.

@DTS Engineer Hello, I am also facing the same error and i have posted it here https://forums.developer.apple.com/forums/thread/768689 with Feedback link https://feedbackassistant.apple.com/feedback/15791497 Can you please validate the encryption for this request as well?

@DTS Engineer Thank you for the response. Could you please explain the differences between launching the app from front of the pass and back of the pass? In case of in-app verification, I understand there will be a button after the card is added to open the relevant mobile app and verify the card. Is this considered the Front of the pass? I assume back of the pass is the info icon that we have for any selected payment card where there can be an associated link to a mobile app

@DTS Engineer Thanks for the response. In the case of yellow flow in-app verification, the user will add the card manually to the wallet app. I assume the serialNumber will be generated for the card once it is added to the wallet and pending verification. In this case, how do we include serialNumber in the payload of our app launch URL since appLaunch URL is something we configure in the PNO portal and will not have the serialNumber at the time of configuration?

@mmysliwiec I am also stuck with the same issue. In our case, I am testing In-app provisioning in our test production app which has different ADAM ID as that of the one given for apple for allow listing. But the associatedApplicationIdentifiers are correcty configured for both the apps. Is there a requirement that Apple needs to allow our Application Identifiers/ADAMID to query for passes?