[Due for payment 2026-08-05] Android - Agents - Back button disappears after rotation

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.45-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #94565
Email or phone of affected tester (no customers): testing210790@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung a31
App Component: Other

Action Performed:

1. Open the Expensify app and log in with a new Gmail account.
2. Navigate to Account settings.
3. Tap Agents.
4. Tap New Agent.
5. Tap Write custom instructions.
6. Rotate the device to landscape mode.
7. Enter multiline text in the custom instructions field.
8. Rotate the device back to portrait mode.

Expected Result:

The Back button remains visible after changing the device orientation, allowing the user to navigate back normally.

Actual Result:

The Back button disappears after rotating the device from landscape mode back to portrait mode while creating a new agent. The user cannot see the navigation back control in the header. Create agent button overlaps the avatar on different device, custom instructions is unavailable

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7219160_1785183536334.WhatsApp_Video_2026-07-27_at_4.07.06_PM.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7219160

Issue Owner

Current Issue Owner: @Krishna2323

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/316302c20dd1b5f16fafbbfe9469c458ab952c1e181b4b5a5dfeba99520ceb5c

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #94565

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #94565 - "Fix Agents - Input field does not auto scroll down when entering next line" by @GCyganek (High confidence)
Related Issues: #93631 (the issue #94565 was fixing)

Recommendation: REVERT

PR #94565 introduced the CollapsibleHeaderOnKeyboard wrapper around the Agents header, and its collapse/restore logic leaves the header clipped and slid off-screen after a landscape→portrait rotation with the keyboard open — this is exactly the reported symptom, is native-only, and reverting cleanly removes the regression while returning the (pre-existing, non-blocking) auto-scroll issue to its backlog.

Assigned: @GCyganek (PR author), @NicolasBonet and @truph01 (approving reviewers) from PR #94565
Labels: No change. Kept DeployBlockerCash (App deploy is correctly blocked). DeployBlocker was not present, so nothing to remove.

📋 Detailed Analysis

Evidence

• The bug flow (Settings → Agents → New Agent → Write custom instructions → rotate landscape → type multiline → rotate back to portrait) exercises AddAgentPage, whose header PR Fix Agents - Input field does not auto scroll down when entering next line #94565 newly wrapped in <CollapsibleHeaderOnKeyboard>. The same change was applied to EditPromptPage.
• The CollapsibleHeaderOnKeyboard component and all of the code paths involved are new in / finalized by PR Fix Agents - Input field does not auto scroll down when entering next line #94565 — the full commit history of src/components/CollapsibleHeaderOnKeyboard/index.native.tsx belongs to the @GCyganek/landscape-mode/agent-prompt-multiline branch (PR Fix Agents - Input field does not auto scroll down when entering next line #94565), merged 2026-07-27, which lines up with the first staging build the bug appears in and matches "Reproducible in staging: Yes / production: No."
• The web entry src/components/CollapsibleHeaderOnKeyboard/index.tsx is a no-op that renders children as-is, so only native is affected — consistent with the report of "Android App only."
• No other PR on the current StagingDeployCash checklist (Deploy Checklist: New Expensify 2026-07-27 #97134) touches the Agents custom-instructions screens or this header/orientation logic.

Verification

• Affected files (all modified by PR Fix Agents - Input field does not auto scroll down when entering next line #94565):
  • src/components/CollapsibleHeaderOnKeyboard/index.native.tsx — the collapse/restore worklet and orientation-restore effect
  • src/pages/settings/Agents/AddAgentPage.tsx — header wrapped in CollapsibleHeaderOnKeyboard (the screen in the repro)
  • src/pages/settings/Agents/Fields/EditPromptPage.tsx — same wrap
• Confirmed via gh pr view 94565 --json files that these paths are in the PR, and via the file commit history that the component was introduced on the PR's branch.

Root Cause

In src/components/CollapsibleHeaderOnKeyboard/index.native.tsx:

1. In landscape with the keyboard open, the useAnimatedReaction collapses the header by setting animatedHeight to a small target (lines 165-176). While collapsed, outerStyle clips the header (height: animatedHeight, overflow: 'hidden') and innerStyle slides it up by translateY = animatedHeight - naturalHeight (lines 181-201). At this point the back button is intentionally hidden.
2. Rotating back to portrait fires the orientation-restore effect at lines 99-105, which restores animatedHeight to naturalHeight only when naturalHeight.get() !== -1 — a value that is only ever captured in onLayout.
3. The UI-thread reaction that would otherwise restore on keyboard state change bails out immediately in portrait because of if (!isFocusedSV.get() || !isInLandscapeModeSV.get()) return; (line 137). So once in portrait, the reaction can no longer un-collapse the header.
4. This leaves a race between the one-shot orientation effect (which reads naturalHeight/sets animatedHeight on the JS→UI hop) and the portrait onLayout re-sync at lines 82-87. On Android the keyboard height only reaches its final value on onKeyboardMoveEnd, so the collapse/threshold timing differs from iOS and the header can end the rotation still clamped at the collapsed animatedHeight (slid off-screen by the negative translateY). The result: the header stays clipped/translated and the Back button is not visible — exactly the reported bug, native/Android-only.

The fix intent of PR #94565 (auto-scroll multiline input in landscape) is unrelated to and does not depend on shipping this header-collapse behavior, so a straight revert is safe.