Android - Expense - Split page is completely obstructed when keyboard is opened

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.54-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #85229
Email or phone of affected tester (no customers): jsdjosidjiojisojio3@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Money Requests

Action Performed:

1. Launch Expensify app in landscape mode.
2. Go to workspace chat.
3. Create an expense.
4. Open the report.
5. Tap More > Split.
6. Tap on any split amount input.

Expected Result:

The focused amount field should be visible when keyboard is opened.

Actual Result:

Split page is completely obstructed when keyboard is opened.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7124271_1775608962158.05.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @GCyganek

[melvin-bot]

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

[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.

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #85229 - "Unlock landscape mode" by @GCyganek (High confidence)

Recommendation: REVERT

PR 85229 unlocked landscape mode on Android and iOS phones, but SplitExpensePage does not properly handle keyboard avoidance in landscape mode, causing the split page to be fully obstructed when the keyboard opens. Reverting restores portrait-only orientation locking and eliminates the regression.

Assigned: @GCyganek (PR author), @rushatgabhane @truph01 @mjasikowski (approving reviewers)
Labels: Keeping DeployBlockerCash (Frontend bug in App). Removing DeployBlocker (no backend changes required).

Evidence:

• Reproducible on staging only (new feature, not in prod), aligns with PR 85229 being in staging release 9.3.54-0 (merged 2026-04-07).
• melvin-bot directly assigned this bug to PR 85229.
• Bug manifests specifically in landscape mode on Android when keyboard opens - PR 85229 is precisely the change that unlocked landscape mode for phones.
• The PR removed portrait-only orientation locks from android/app/src/main/res/values/orientation.xml and android/app/src/main/java/com/expensify/chat/MainActivity.kt.

Verification:

• Affected flow: workspace chat > expense > open report > More > Split > tap any split amount input.
• PR 85229 adds landscape handling for bottom-docked modals in src/components/Modal/BaseModal.tsx (max-height + ScrollView wrapping), but SplitExpensePage is a full navigation stack screen, not a bottom-docked modal, so this fix does not apply to it.
• SplitList renders SelectionList with inline TextInput fields without landscape-aware keyboard avoidance logic.
• SplitExpensePage uses ScreenWrapper with shouldEnableMaxHeight={canUseTouchScreen()} but no landscape-specific keyboard avoidance was added.

Root Cause:
PR 85229 unlocked landscape mode globally for Android phones by removing the orientation restriction files, but added landscape keyboard handling only for bottom-docked modals via BaseModal.tsx. SplitExpensePage is rendered as a full navigation stack screen. On Android in landscape mode, the OS does not automatically shrink the viewport when the keyboard appears. Without landscape-aware keyboard avoidance in SplitExpensePage or its SplitList/SelectionList children, the keyboard fully covers the focused split amount input field.