Why Live Activity updates silently fail
Stale tokens, payloads that don't match ContentState and Apple's priority budget, and how to catch each one.
APNs answers 200 and nothing changes on the Lock Screen. It is the most common Live Activity bug, and it almost always
has one of three causes.
1. A stale token
Every activity has its own update token, and the push-to-start token rotates. If your backend keeps the first one it saw, later pushes go nowhere. The SDK reports each new token as soon as iOS hands it over, even after a background launch, and devices that got their token late catch up on the latest state.
2. A payload that doesn’t match ContentState
iOS decodes content-state into your app’s ContentState struct. A missing key, a string where the struct has an Int
or a Date sent in the wrong format, and the update is dropped without an error. Swift’s default Codable encodes
Date as seconds since 2001, not Unix time.
We compare every content state with what your app’s ContentState sends: same keys, same JSON types, and under APNs’
4 KB limit. A mismatch returns 422 with the field that differs.
3. The priority budget
Priority 10 updates count against an hourly budget Apple doesn’t publish. Spend it on routine progress and the
system starts throttling. Updates go at priority 5 unless they carry an alert, and rapid updates collapse into the
newest one.
Seeing it
Each activity’s timeline in the dashboard lists every push, APNs answer and SDK report in order, and delivery.failed
and token.invalid webhooks tell your backend as it happens.