Wallet Pass

In short

Almost every Wallet Pass problem of the year had one of four causes: coordinates typed wrong in Locations, a field changed on the Settings tab, an empty custom field added to the pass, or a text changed without updating the passes. Check those four before anything else. The page itself is described in Wallet Pass.

Check first

1. Locations: every latitude and longitude with a decimal point, the minus sign where it belongs (western longitudes, for instance in Spain), and the full precision. A comma, a missing sign or a missing point in one location can block the updates of every pass.
2. Settings tab: untouched. The Pass Type Identifier and the signing fields must stay as delivered.
3. Fields tab: no custom field added and left empty, and the header still showing the credit balance.
4. After a text change: enough time passed for the phones to refresh, or your provider pushed the update.

Causes and fixes

Passes stopped updating

The last location added had a longitude without its decimal point. One invalid location blocked the update of every pass of the club. Since then one bad location no longer blocks the others, but a wrong coordinate still means no proximity message and a wrong map pin.

Fix: correct the coordinates, then ask your provider to push the update to every pass (the Update all passes button on the Passes tab is for your provider to use, not for routine use).

The pass cannot be added on iPhone, or on Android

• Every iPhone pass failed in a club where someone changed the Pass Type Identifier on the Settings tab. Those fields tie the pass to the certificate; a changed one breaks every pass already installed. Your provider restores the fields, and members who hold the old pass delete it and download it again.
• Google Wallet refused the pass in two clubs: in one a custom field had been added and left empty; in the other an empty field had been added and the header's credit balance replaced by another field. Delete the empty field, put the credit balance back, and the pass adds again.
• The "Add to Wallet" button does not show in browsers that do not declare Wallet support: a link opened inside another app, or an unusual browser. Open the app in Safari or Chrome.

A text or image change is not visible on phones

Texts changed in Fields or Design reach a phone when the pass refreshes. If the change must reach every phone now, ask your provider to push it (Update all passes, on the Passes tab, is for your provider). A new image reaches phones only after that push; adding the pass again does not fetch it.

No proximity notification

The proximity message shows on iPhone only, for at most 10 locations, each with correct coordinates. The icon shown with it needs an opaque background; a transparent one never updates on the phone. And the member's phone must allow the Wallet app to use location.

Levels do not show on the pass

Conditional views swap the look of the pass by tag, and on Android only the strip image swaps. A level without its own strip image shows nothing. Upload one image per level under Conditional views on the Design tab.

When to write to your provider

Write when a Settings tab field was changed, when a pass fails on every phone after the checks above, or when a text or image change must reach every phone now. Send the club, a screenshot of the Locations tab, and one member's phone or email whose pass fails. See How to ask for help.