[Bug]: iOS 2.1.0 thread list misses days of threads from online environments; survives force-quit, fixed by toggling the environment #24997

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/mobile

Steps to reproduce

Setup: the iOS app is paired to two environments (a MacBook and a Windows desktop), both online. The desktop app on the MacBook is also connected to the Windows environment.

1. Use both machines normally for a few days, creating threads from desktop and from the phone.
2. Open the iOS app's Threads list ("All environments", "All projects").
3. Compare it with the desktop sidebar.

I don't have a reliable repro for how the phone gets into this state.

Expected behavior

The mobile thread list matches the desktop sidebar for the same environments.

Actual behavior

The mobile list was missing almost every thread created or updated in the previous ~4 days, across both environments. After the pinned threads, the list went from one thread updated a few minutes earlier straight to threads last active 4 days ago.

• The only recent threads that appeared were pinned ones and one thread I had opened on the phone that day. Several missing threads had been created from the phone (creationSource: mobile).
• The missing threads were not settled or snoozed. Desktop showed all of them.
• Force-quitting and reopening the app did not fix it.
• Turning the MacBook environment off and back on in the mobile app fixed it: the missing threads appeared right away.

So the phone seems to keep showing a saved copy of the thread list and does not replace it with the full snapshot it loads, until the environment is reset.

Impact

Major degradation or frequent failure: threads were silently missing with nothing showing the list was out of date.

Version or commit

iOS app 2.1.0. MacBook server 0.1.2 (T3 Code (Beta) desktop, macOS arm64).

Environment

iPhone (iOS 27) paired to a macOS arm64 laptop and a Windows desktop.

Logs or stack traces

Server traces from the MacBook while the phone was showing the incomplete list. The phone loaded the full shell snapshot successfully, then its subscription ended about 40–100 s later:

13:38:56 ShellStream.loadShellSnapshotParts      Success  69ms
13:38:56 http.orchestration.loadShellSnapshot    Success  69ms
13:38:56 ws.rpc.orchestration.subscribeShell     Interrupted after 98s
13:40:37 ShellStream.loadShellSnapshotParts      Success  78ms
13:40:37 http.orchestration.loadShellSnapshot    Success  79ms
13:40:37 ws.rpc.orchestration.subscribeShell     Interrupted after 39s

Over the same period the server's thread list (t3_thread_list) returned every missing thread as unsettled and not snoozed. I have no runtime logs from the phone.

Related: #24530 (cached threads from an offline machine shown as current; here the environment was online), #24344 (iOS 2.1.0 stale state for newly created threads, but that one clears on app restart), #24909 (iOS 2.1.0 short-lived sockets).