Also what I’ve observed is:
Once the app is launched at least once, it seems Airship (or the system) is able to track and associate Live Activities, because even after the app is terminated or removed from background, updates to the Live Activity continue to work correctly.
However, if the app has never been opened, or hasn’t been opened in a long time (e.g. the device was restarted, or the app was force-quit and never relaunched), then:
Live Activity may start via push, but updates do not get delivered
On some devices, Live Activity doesn’t even appear despite receiving the push
This leaves me wondering:
🔍 How is iOS handling and routing Live Activity push updates under the hood?
Does iOS store the push token → activity name mapping internally?
Or does the app need to explicitly track and restore this every time?
What factors (e.g. app state, device state, APNs token lifecycle) affect whether the activity shows up or gets updated?
I'm trying to understand the system behavior and what assumptions I can make to support edge cases like first-time users or long-time inactive installs.
Any guidance from Apple or the community would be greatly appreciated!
Topic:
App & System Services
SubTopic:
Widgets & Live Activities
Tags: