Hi,
Our iOS airline app already provides its own Live Activity for flight tracking. We are currently adopting Apple's semantic boarding pass for our Wallet boarding passes.
According to Apple's documentation, to automatically suppress the Wallet-based Live Activity, we should add our App Store Identifier (Adam ID) to the associatedStoreIdentifiers array in pass.json.
We have configured this as follows:
"associatedStoreIdentifiers": [ "<OUR_APP_STORE_ID>" ]
However, we are still seeing the Flight Tracker / Wallet-based Live Activity option for the flight after adding the semantic boarding pass to Wallet.
Has anyone experienced this behavior?
Specifically:
Is associatedStoreIdentifiers expected to completely suppress the Wallet-generated Live Activity?
Does it suppress only the automatically generated Live Activity, while the Flight Tracker functionality remains available in the semantic boarding pass?
Are there any additional requirements or specific pass.json configurations needed?
Does the pass need to be removed and re-added to Wallet after adding associatedStoreIdentifiers?
Is this behavior different between iOS versions?
Our objective is to prevent duplicate flight-tracking Live Activities because our application already provides its own Live Activity for the same flight.
Any clarification or guidance would be appreciated.
Thanks!