Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Android] Back navigation broken on foldables after switching conversations on large screen

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

On Android foldable devices, the back stack accumulated by switching between conversations on the large (unfolded) screen does not collapse when the device folds back to the small screen. Pressing the system back button cycles through previously visited conversations instead of returning to the conversation list that the small-screen layout shows as the parent destination.

Root Cause

On Android foldable devices, the back stack accumulated by switching between conversations on the large (unfolded) screen does not collapse when the device folds back to the small screen. Pressing the system back button cycles through previously visited conversations instead of returning to the conversation list that the small-screen layout shows as the parent destination.

RAW_BUFFERClick to expand / collapse

Summary

On Android foldable devices, the back stack accumulated by switching between conversations on the large (unfolded) screen does not collapse when the device folds back to the small screen. Pressing the system back button cycles through previously visited conversations instead of returning to the conversation list that the small-screen layout shows as the parent destination.

Steps to reproduce

  1. Open Claude Code on an Android foldable, unfolded (large screen / multi-pane list-detail layout, conversations list visible on the left).
  2. Tap conversation A, then B, then C. Each one becomes the active detail pane.
  3. Fold the device to the small screen (single-pane layout — only the active conversation is visible, with the conversations list reachable via back).
  4. Press the system back button.

Expected

A single back press returns to the conversation list (the parent destination visible in the small-screen layout).

Actual

Each back press pops one entry off the conversation-switch back stack: C → B → A → list. Three back presses to return from a state where the small-screen layout shows no in-app history at all.

Why this is a foldable-specific bug

In the multi-pane (large-screen) layout, switching the detail pane does not move the user away from a "conversation list" parent — both panes are visible simultaneously. Switching detail conversations on large screen should therefore not contribute back-stack entries that the small-screen layout will later treat as ancestors. Android's recommended pattern (`SupportingPaneScaffold` / `ListDetailPaneScaffold` with `BackNavigationBehavior`) handles this by collapsing detail-pane history on layout-class transitions.

Environment

  • Claude Code Android client
  • Foldable device (e.g. Pixel Fold, Samsung Galaxy Z Fold, Surface Duo)
  • Triggered by transition from `WindowWidthSizeClass.Expanded` → `WindowWidthSizeClass.Compact` while a non-list destination is active.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#LLM response#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING