Apple Wallet problems look similar from the outside, but the fix depends on where the failure happens. A pass that will not download is a browser or issuer-link problem. A pass that will not scan is usually a barcode, brightness, or venue-policy problem. A pass that will not update is usually controlled by the issuer backend, not by Wallet itself.
Use this page as the hub. Start with the symptom in the matrix, then open the detailed guide for the exact failure mode.
Troubleshooting matrix
| Symptom | Likely cause | Quick fix | When NeatPass helps | Guide |
|---|---|---|---|---|
| Pass keeps old data | Issuer has not published a fresh pass version | Open the issuer app, check for a newly issued pass, then re-add it | Useful when the source is a static barcode you can rebuild | Read |
| Pass cannot be deleted | Expired pass view, sync state, or issuer restriction | Check hidden expired passes and remove the active copy first | Not needed, this is Wallet library cleanup | Read |
| .pkpass opens as a file | Browser or server did not hand the file to Wallet correctly | Open the original link in Safari and avoid in-app browsers | Useful if the original ticket also exposes a static barcode | Read |
| Chrome cannot add the pass | Chrome download flow breaks the Wallet handoff | Use Safari for the same link | Use NeatPass only when no valid pkpass is available | Read |
| Safari cannot download pkpass | Expired link, broken redirect, VPN, or issuer-side headers | Request a fresh link, disable VPN, and retry on mobile Safari | Useful for static barcode fallbacks | Read |
| Unable to add pass | Duplicate, device-bound, expired, malformed, or blocked pass | Use a fresh issuer link and remove stale copies before retrying | Works only when the barcode is static | Read |
| Barcode will not scan | Wrong format, poor source image, brightness, or dynamic code | Check barcode type, rebuild from a sharp source, and keep backup | Useful for supported static barcodes | Read |
| Scanner cannot read screen | Display brightness, glare, screen protector, or old scanner | Raise brightness and present the barcode squarely | Can rebuild a cleaner pass when the source data is valid | Read |
| Pass disappeared after update | Wallet reindexing, hidden expired passes, or iCloud sync delay | Search Wallet, check expired passes, then re-add from issuer | Useful if the original source still has a static barcode | Read |
| Pass not on lock screen | Missing relevance date, location, or notification settings | Open Wallet manually or rebuild with better date details | Useful for custom passes with clear date or location fields | Read |
| Shared pass will not work | Issuer disabled sharing or bound the ticket to one device | Use the official transfer flow instead of copying the pass | Cannot bypass issuer device limits | Read |
Pass will not add
Add failures usually start before Wallet has a valid pass. If a `.pkpass` file opens as a download, use the pkpass detection guide. If the issue only happens in Chrome, switch to Safari and use the Chrome to Safari fix. If Safari itself fails, check the Safari pkpass guide before rebuilding the pass.
Apple's own Wallet flow can also show a generic unable to add message. That usually means the pass is expired, duplicated, malformed, device-bound, or blocked by the network. The unable to add pass guide is the right starting point for that error string.
Pass is in Wallet but looks wrong
Wallet does not invent updated ticket data. If a gate, seat, balance, or date is stale, the issuer has to publish a new pass version. Start with Apple Wallet pass not updating. If the pass disappeared after an iOS update, check the disappeared-pass guide. For lock screen timing, use the lock screen guide and the help article on lock screen widgets.
Barcode will not scan
A scanner reads barcode data, not the app name. For static barcodes, Wallet can work as well as a PDF or plastic card when the format and source image are correct. Check the supported barcode formats and the barcode detection help article before assuming the venue has blocked Wallet.
If a barcode works in the official app but not from a screenshot or custom pass, it may be dynamic. Ticketmaster SafeTix and similar systems intentionally rotate the barcode. NeatPass cannot convert those. The right path is the official app or the issuer's own Add to Apple Wallet button.
Apple Watch and sharing issues
Apple Watch sync depends on the iPhone Wallet copy and Watch settings. Open the pass on iPhone first, then check the Watch app. Sharing is separate. Apple lets issuers decide whether a pass can be shared, so a missing share button usually means the issuer disabled it. See the shared pass guide and Apple's broader Wallet issues help page.
Bereit, deine Karten zu migrieren?
Mit NeatPass kannst du ganz einfach jedes Ticket, jeden Pass oder jede Kundenkarte in Apple Wallet umwandeln.
Frequently asked questions
Related guides
For broader context, read why passes belong in Apple Wallet, how to convert any supported barcode, and what to do when there is no Add to Wallet button.