[Bug]: Android thread content overlaps after switching directly between threads

[fionn77]

Before submitting

• I searched existing issues and did not find a native Android report with this thread-switching reproduction.
• I included reproduction details, a reliable workaround, and screenshots.

Area

apps/mobile on Android.

Thanks for building and supporting the mobile app. I am reporting this in case the reproduction and screenshots help isolate a state or layout-measurement issue; this is not meant as a complaint.

Steps to reproduce

1. Open the official T3 Code Android app on a Google Pixel 7a.
2. Open a thread, especially one with a longer conversation or an active turn.
3. Return to the thread list.
4. Immediately open a different thread.
5. Repeat the direct thread-to-thread switch if necessary; the issue is intermittent but occurs regularly for me.

Expected behavior

The newly selected thread should render only its own current content, with every message, activity indicator, tool/result block, and timestamp occupying the correct vertical space.

Actual behavior

After switching directly between threads, the newly opened thread can render with badly stale or incorrect layout:

• user bubbles overlap assistant content;
• assistant text and result blocks stack on top of each other;
• the Working for ... indicator appears behind or inside unrelated content;
• long responses can be drawn in several overlapping columns;
• parts of the timeline become difficult or impossible to read.

Leaving the affected thread and opening it again makes the same content render correctly. That recovery makes me suspect stale thread state or cached row measurements during a fast thread change, but that is only a guess.

One screenshot also contains a Checkpoint capture failed message. I do not know whether that error is related to the rendering problem, so I am including it only as an observation rather than claiming the same cause.

Impact

Significant visual degradation. No data loss observed, but the conversation can be unreadable until the thread is reopened.

Version or commit

Android app version / OTA identifier not captured. Observed on August 4, 2026.

Environment

• Official T3 Code native Android app
• Google Pixel 7a
• Dark appearance
• Android OS version not captured

Screenshots

Workaround

Return to the thread list and reopen the affected thread. It then loads and lays out correctly.

Possibly related

• Long messages can break chat layout after window changes #458 reports overlapping rows after desktop window/layout changes and suspects stale virtualized-row measurements.
• Chat timeline content overlaps (assistant text + tool call cards stack on top of each other) #1035 reports desktop timeline content stacking on top of other blocks.

Those reports look related at the symptom level, but neither describes the native Android thread-switching trigger or the reopen workaround.

I am happy to test a fix or provide the exact app/OTA and Android version if maintainers point me to where those identifiers are shown.