We are observing multiple different deviceId values linked to the same user within short timeframes. In some instances, a new deviceId appears every few minutes or hours. We utilize this identifier for managing Apple Wallet pass updates.
We would appreciate understanding which scenarios might cause the deviceId to change. Could it be influenced by:
Device restoration or factory reset procedures
App reinstallation or data clearing
iOS version updates
iCloud account changes or Apple ID authentication status changes
Privacy feature activation (such as App Tracking Transparency or Private Relay)
Testing environment usage (simulators or automated testing frameworks)
We aim to determine whether this behavior is expected or if it suggests atypical usage patterns.
Thank you for your assistance!
Wallet
RSS for tagDiscuss how to manage tickets, boarding passes, payment cards and other passes in the Wallet app.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
For our project we publish and endpoint to update a PKPass from wallet. It works fine.
We are facing a problem with expired passes, due to the Automatic Updates configuration in each device our server received a lot request included those from expired passes. I cannot find any configuration inside the pass to avoid this request to my server.
Hello,
We are trying to provision in apple wallet, I am getting an error "Card can not be added".
Please check below and let me know if I am missing anything.
SEID: 04401D7BCE578001930001236930311377D86C15D956BBA1
TimeStamp: 2025-08-18 11:53:04.570431-0500. CST
Last 4 FPAN: 2345
Thanks
Good day)
Colleagues, please tell me how can I change the notification on the locked screen "pass changed" in PKPASS when changing several fields?
Thank you very much for your answer
We have Wallet and Watch application on iPhone.
Both of them can add card and then waiting for activation.
However, When the same card is added to Wallet and Watch respectively, waiting for the app-to-app mode to be activated.
Client doesn't aware the source application.
Because deeplink is exactly the same.
Any adivse how does the client have to choose which card to activate?