[Bug]: Android work-log list crashes with "Maximum update depth exceeded" during active subagent work

Offen
  • Stimmt etwas nicht?
#34,031 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
52/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
react-native, typescript
Bereich
frontend, mobile

Rechercherichtung

Start in the mobile app’s ThreadWorkGroupList and trace its use of AnimatedLegendList; the issue localizes the update-depth error there but does not identify a root cause. Compare the list’s subscription and layout updates while work-log activity streams, then reproduce on Android with an active helper if possible. Done means the thread view stays usable during streamed tool activity without the update-depth error.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

A deterministic minimal reproduction has not yet been isolated. Observed scenario:

  1. Use the T3 Code Android app to view a long-running thread connected to a Windows host.
  2. The thread has a running Claude Agent turn with an active helper/subagent producing tool activity.
  3. The mobile thread view fails with Maximum update depth exceeded. The component stack runs through ThreadWorkGroupList and its nested AnimatedLegendList, under a DisclosureRow.

The thread had approximately 2,633 top-level timeline items across 50 runs when inspected. The active helper had performed over 100 tool uses. These are context, not established reproduction requirements. The exact gesture or update immediately preceding the error (opening, expanding, scrolling, or a streamed update) is unknown.

Expected behavior

The Android thread view remains usable while the agent and its helper stream tool activity.

Actual behavior

React throws an update-depth error in the mobile work-log list.

Read-only inspection of the host immediately afterward confirmed that the affected run and its helper were still running, with fresh tool results and a subsequent test-game launch in the provider log. The failure therefore affected the client display while backend work continued.

No host restart, thread interruption, data deletion, or configuration changes were performed during diagnosis.

Impact

Major degradation or frequent failure

The affected Android thread view fails; backend work continues. Reproduction frequency has not been established.

Version or commit

Windows host desktop/server installation: 0.1.9-nightly.20261110.4465, read from the host's desktop-last-started-version.

Android client version/build and commit: not yet captured. The host version should not be treated as the Android client version.

Environment
  • Client: native T3 Code Android app (com.t3tools.t3code), Expo bundle.
  • Phone model and Android version: not yet captured.
  • Host: Windows; T3 Code Nightly.
  • Provider: Claude Agent, with an active helper/subagent.
  • Observed November 10, 2026, around 19:15–19:17 UTC.
Logs or stack traces

Relevant excerpt of the user-visible error below. Identical repeated frames are abbreviated; bundle offsets are retained.

Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
    at enqueueConcurrentRenderForLane (bundle:1:2656200)
    at updateStoreInstance (bundle:1:2662076)
    at commitHookEffectListMount (bundle:1:2694735)
    at commitPassiveMountOnFiber (bundle:1:2707897)
    at recursivelyTraversePassiveMountEffects (bundle:1:2706866)
    ... repeated passive-mount traversal frames; original trace skips 602 frames ...
    at flushPassiveEffects (bundle:1:2727716)
    at flushPendingEffects (bundle:1:2727499)
    at flushSpawnedWork (bundle:1:2727214)
    at commitRoot (bundle:1:2726179)
    at completeRootWhenReady (bundle:1:2713817)
    at performWorkOnRoot (bundle:1:2713082)
    at flushSyncWorkAcrossRoots_impl (bundle:1:2652976)
    at anonymous (bundle:1:7828190)

Component stack:
    at ContainersLayer2 (bundle:1:6621412)
    at Containers2 (bundle:1:6621928)
    at RCTView
    at View (bundle:1:2598473)
    at RCTScrollView
    at ScrollView (bundle:1:2946037)
    at ScrollView (bundle:1:2949105)
    at ScrollView (bundle:1:2911254)
    at AnimatedComponent(ScrollView) (bundle:1:7956644)
    at ScrollView (bundle:1:7956701)
    at AnimatedScrollView (bundle:1:3146147)
    at ReanimatedScrollBridgeComponent (bundle:1:6555513)
    at ListComponent2 (bundle:1:6622933)
    at LegendListInner2 (bundle:1:6626035)
    at StateProvider (bundle:1:6559227)
    at LegendList2 (bundle:1:6625770)
    at LegendListForwardedRef2 (bundle:1:6557277)
    at AnimatedComponent(Component) (bundle:1:7956644)
    at Component (bundle:1:7956701)
    at AnimatedLegendList2 (bundle:1:6557680)
    ... View wrappers ...
    at ThreadWorkGroupList (bundle:1:7017735)
    ... View wrappers ...
    at WorkLogBlock (bundle:1:7042214)
    at ThreadWorkLog (bundle:1:7015012)
    at ThreadMediaVisibility (bundle:1:7189355)
    at MessageImageGalleryScope (bundle:1:7204101)
    ... View / animated View wrappers ...
    at DisclosureRow (bundle:1:7202939)
    ... View wrappers ...
    at PositionViewState2 (bundle:1:6618328)
    at Container2 (bundle:1:6619875)
    at ContainerSlotBase (bundle:1:6605679)
    at ContainerSlot2

Here bundle stands for:
/data/user/0/com.t3tools.t3code/files/.expo-internal/42bac505bc3eda455134bc0b498d30dc.

Investigation notes

The stack localizes the failure to the grouped work-log list, but does not establish the root cause. A list snapshot/subscription or layout feedback loop is a hypothesis, not a confirmed diagnosis. No source patch or Android reproduction was attempted.

Related reports found during duplicate search:

  • #21866: Android update-depth crash in the sidebar/inspector path; this trace instead contains ThreadWorkGroupList.
  • #15704: mobile grouped tool-call scrolling problem in the same component, but a different symptom.
Workaround

No workaround has been verified on the affected Android client. Using desktop/web or collapsing the work-log group was suggested, but not tested. The running host and thread were deliberately left untouched.

Private conversation text, thread/environment identifiers, local project paths, and raw provider logs are omitted.

Vorherrschende Sprache
TypeScript
Sterne
24.8k
Forks
6.4k
Ø Merge
10 Std. 56 Min.
Gemergte PRs (30 T.)
226

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus pingdotgg/t3code

Alle Issues in pingdotgg/t3code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.