Repository navigation
Description
Area
apps/mobile
Steps to reproduce
On a test clock, in the existing tests for the Live Activity registration code (not on a device):
- Start a card the way sending a message from the phone does, with no push token available yet.
- Let the token's callback be missed, or let the registration made from it fail.
- Advance 60 seconds with the app in the foreground. Or send the app to the background at 5 seconds and advance eleven minutes.
Expected behavior
While the app is open it keeps trying to register the card. It does not leave a card on the Lock Screen that the relay has no token for.
Actual behavior
After the first attempt nothing retries until the next time the app comes to the foreground, and going to the background leaves the card in place. The relay has no token for that card, so it can neither update nor end it: the card stays at "Connecting" and then reads "Out of date".
A token callback that arrives and registers normally works, so a late token by itself is not the problem.
Impact
Minor bug or occasional failure. When it happens, the Lock Screen and watch show an old status for hours.
Version or commit
main at 6b7027b
Environment
Shown by driving the app's registration code on a test clock, with the native Live Activity module and the relay client mocked. Not checked on a device: no ActivityKit and no push delivery were involved, so this does not show how often a callback is missed or a registration fails on a real phone.
Logs or stack traces
Token never arrives: 0s no token, no retry scheduled; 5s app backgrounds, card left in place; 665s still no registration, retry or end.
Callback missed: 0s no token; 2s token available, nothing runs; 60s still unregistered.
Registration rejected: 2s registration fails, no retry scheduled.
Foreground refresh: 30s the refresh registers an available token (this path does retry).
Workaround
Open the app again. The foreground refresh registers a token that has arrived since.
Related
Where this came from: on 2026-11-13 my phone and watch showed an old thread as "Out of date" for over an hour while two threads were running, and the relay's record for the device held no Live Activity token. That was a build from my fork against a self-hosted copy of the relay, and nothing on the phone confirmed which step failed, so the cause is inferred.
#37329 ios-persistent-live-notification describes the same symptom on the App Store build and was closed as not reproducible. This may be one way to get there.
Sent by Mike's agent (GPT-6.1 Sol in T3 Code, Codex harness)
Activity