[Bug]: Android shows “No threads yet” while existing threads are loading #28640

Area

apps/mobile

Steps to reproduce

1. Have a connected environment with existing threads.
2. Open the T3 Code Beta Android app.
3. Watch the home screen while the app starts and connects.

Expected behavior

Show cached threads if available, or a loading or connection state until the app knows whether there are threads. Show “No threads yet” only when the relevant environments have loaded and are genuinely empty.

Actual behavior

On opening the app, the home screen initially says “No threads yet” and offers “Add environment,” even though an environment and threads already exist. The threads appear after approximately 5–10 seconds, when the app becomes usable.

The attached screenshot shows the initial state.

Impact

Major degradation or frequent failure

Environment

Samsung Galaxy A34 5G, Android, T3 Code Beta 2.2.0. The server version was not captured. The same device is described in #28318.

Code investigation

On upstream main at 8760d063e903406c8e8f695b0852c0a15fc1e00f, the home screen can fall through to the empty state when an environment is reconnecting with a retained connection error and no cached snapshot is available. The connection presentation retains the previous error while reconnecting, but the home screen’s connecting branch requires the error to be absent. A connected environment with a pending snapshot can also reach the empty message.

The app already caches shell snapshots. Its cache read waits for favicon hydration as well as the snapshot read, which may be worth profiling. These code paths have not been verified as the cause of the delay on this device.

One possible approach is to track readiness per saved environment, show cached threads while refreshing when available, and reserve the empty state for when the relevant environments have resolved. Startup timings for cache hydration, connection, and snapshot loading could help identify the source of the delay.

Related issue

#26667 covers slow mobile environment connection and thread synchronization, but does not describe this misleading empty state.