anthropics / anthropics/claude-code
iOS app: routine session view disappears after backgrounding the app
- Vorherrschende Sprache
- Python
- Sterne
- 145k
- Forks
- 23.1k
- PR-Merge-Kennzahlen
- PR-Kennzahlen ausstehend
Beschreibung
## Description
Received a mobile push notification for a scheduled Claude Code routine (a `RemoteTrigger`/cron-based routine, "Issue tackler -> all", `trig_01DfLNAKWChy4S2HAnNtSSff`). Opened the session from the notification on the iOS app. After switching to another app and returning to Claude, the session view was gone — no session content displayed.
## Backend state (verified independently)
The underlying session was not actually lost. Querying `GET /v1/code/sessions?trigger_id=...` and the session's event log via the API afterward showed:
- The run completed successfully (`status: success`) at the expected time.
- Full transcript, tool calls, and the routine's final summary were all present and queryable.
- A push notification had indeed been sent for this run, matching what was received on-device.
So this appears to be a client-side (iOS app) issue — losing/failing to restore the session view on foreground-after-background — rather than any data loss or backend failure.
## Steps to reproduce
1. Have a scheduled routine (webhook or cron trigger) configured to send push notifications on completion.
2. Receive the push notification on iOS and tap into the routine's session.
3. Background the app (switch to another app).
4. Return to the Claude iOS app.
## Expected behavior
The session view should still show the routine's session/transcript, either exactly as left or freshly reloaded.
## Actual behavior
The session view appears empty/gone, as if the session no longer exists, even though it is fully present and queryable via the API.
## Environment
- Platform: iOS app (Claude mobile app)
- Feature: Routines / scheduled triggers, opened via push notification
- Date observed: 2026-09-12/13
Co-Authored-By: Claude Sonnet 5
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.