Repository navigation
Description
What happened
On a Google Pixel 8 Pro running T3 Code mobile 2.2.0, swiping back from Pull Requests closes or leaves T3 Code instead of returning to the Threads list. The user confirmed that the issue persists on 2.2.0.
Expected behavior reported by the user:
- Back from other screens goes back up towards Threads, without exiting the app.
- At the Threads list, the first back gesture keeps the app open.
- Only a second consecutive back gesture from Threads exits the app.
Diagnosis
Source inspection found a plausible gap in Android workspace-root back handling. This is not yet a confirmed diagnosis of the installed mobile build.
The Android workspace root renders Threads and Pull Requests as panes within the same Home route. Selecting the Pull Requests tab changes workspace state rather than pushing a route. WorkspaceRootScreen.android.tsx has no handler that changes the tab to Threads on system Back. PullRequestToolbar.android.tsx registers a back handler only while search is active. A repository search found no double-back-to-exit guard in the mobile source.
Consequently, with search closed and no route to pop, the inspected source is consistent with Android default back handling leaving the app. A device reproduction is still needed to distinguish normal activity exit/backgrounding from a native crash or a predictive-back dispatch problem.
The individual PR detail screen has a different handler, useAndroidWorkspaceBack("pullRequests"), which returns to the PR list. That handler alone does not implement the requested return-to-Threads and root exit policy.
Steps to reproduce
Reported flow, to verify on the affected build:
- Open T3 Code on the Pixel 8 Pro.
- Open the Pull Requests section.
- Swipe inward from the screen edge to invoke Android system Back.
- Observe that the app closes/leaves the foreground instead of returning to Threads.
Follow-up acceptance checks: Back from Pull Requests reaches Threads; first Back at Threads keeps the app open; the second consecutive Back at Threads exits. Also verify keyboard/search dismissal, individual PR details, Settings, and that navigating elsewhere clears any pending exit confirmation. Confirm the exact originating PR screen during device reproduction.
Version
Affected mobile app version: 2.2.0, confirmed by the user. Mobile build number/update identifier: unknown. Exact Android version/build: unknown; user describes it as the latest Android.
The connected server reports 0.1.5-nightly.20261029.3877. This is the host server version, not evidence of the installed mobile app version.
Environment
Google Pixel 8 Pro; Android native mobile app; Android system back gesture. Host server runs on macOS arm64. No current triage context file was supplied in this scratch thread.
Evidence
Source inspected in local checkout 6d450a4. The three relevant files below were independently confirmed byte-identical to upstream main at b42adff on 2026-10-30:
- Android workspace root: tab panes within Home, no root back/exit guard.
- PR list toolbar: back listener only while searching.
- Android detail back handling: separate detail-to-list behavior.
Evidence is user report plus source inspection. No phone/emulator reproduction, native crash logs, or automated regression test was collected. Upstream app.config.ts also defaults the mobile version to 2.2.0; this version string alone does not pin the installed build or over-the-air update to a source commit. Follow-up searches and the workspace-root history check did not identify a shipped fix for the reported root-tab exit. A newer mobile build resolving this remains unconfirmed.
Related issues
Issue #24753 concerns Back from a PR opened inside a chat returning to the PR list instead of the originating chat. PR #27050 addresses that history-preservation problem and was open/unmerged when checked. Neither describes the root PR-tab exit or the requested two-gesture exit policy. Searches found no exact duplicate; duplicate status remains subject to confirming the affected screen/build.
Fix applied or workaround
No source, application state, installation, or settings were changed. Select Threads directly using the navigation tabs as a temporary way to avoid the reported PR-screen back gesture. This does not add exit protection.
Filed by
Draft prepared by GPT-6.1-Sol via Codex in T3 Code triage.
Activity
fix(mobile): Android Back from Pulls or Usage returns to Threads
fix(mobile): Android Back from Pulls or Usage returns to Threads