[Due for payment 2026-05-20] [Due for payment 2026-05-18] Split - The input field loses focus while typing the split amount.

[lanitochka17]

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.69-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-27459/folder/13176791/41237172/1401785230?sort=%2Bidentifier
Email or phone of affected tester (no customers): applausetester+abr2@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Web, Android, IOS
App Component: Other

Action Performed:

1. Go to staging.new.expensify.com.
2. Open any workspace chat.
3. Create an expense.
4. Open the created expense and click More → Split.
5. Try entering an amount such as “22”.

Expected Result:

The amount input field should remain focused.

Actual Result:

The input field loses focus while typing the split amount.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7148584_1778260922260.2026-05-08_19-20-35.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @truph01

[melvin-bot]

Triggered auto assignment to @puneetlath (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[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: #88178 - "Fix input hidden behind keyboard/header in landscape mode" by @GCyganek (High confidence)
Related Issues: #87312, #87308, #87377, #87403, #87405, #87415

Recommendation: REVERT

PR #88178 introduced a useHandleInputFocus hook into SplitList/index.tsx whose return value is not memoized, causing a new function reference on every render. This makes the SplitListItemWithInputFocus component — which depends on that function in its useMemo — recreate on every render, forcing SelectionList to remount list items and causing the input to lose focus while typing.

Assigned: @GCyganek (PR author), @truph01, @mjasikowski (approving reviewers)
Labels: DeployBlockerCash kept (frontend App PR is the cause). No label changes made.

Detailed Analysis

Evidence

• PR Fix input hidden behind keyboard/header in landscape mode #88178 (merged 2026-05-08, same day as the bug report) modified src/pages/iou/SplitList/index.tsx and introduced src/pages/iou/SplitList/useHandleInputFocus/ — the exact files that control how split input focus is managed.
• The bug is staging-only and was introduced in version 9.3.69-0, which aligns with the merge date of this PR.
• The bug reproduces on Web, Android, and iOS — matching the cross-platform impact of the refactored hook.

Verification

• Affected files: src/pages/iou/SplitList/index.tsx, src/pages/iou/SplitList/useHandleInputFocus/index.ts, src/pages/iou/SplitList/useHandleInputFocus/index.android.ts
• PR Fix input hidden behind keyboard/header in landscape mode #88178 directly modifies all of these files — confirmed via gh pr view 88178 --json files.

Root Cause

In the old code (SplitList.tsx before the PR), handleInputFocus was created with useCallback((...) => {...}, []) — a stable reference.

In the new code, handleInputFocus is assigned the return value of useHandleInputFocus({listRef}). Neither index.ts nor index.android.ts wraps the returned function in useCallback, so a new function reference is produced on every render.

SplitListItemWithInputFocus is created via useMemo(..., [handleInputFocus]). Because handleInputFocus is a new reference on every render, useMemo invalidates and creates a new component type. When SelectionList receives a new ListItem prop, it unmounts and remounts the current list item, causing the text input inside it to lose focus on each keystroke.

The useLandscapeOnBlurProxy changes (also in this PR) affect Android portrait-mode behavior as well: the new isKeyboardOpening guard can trigger a refocus setTimeout during normal typing in landscape mode, compounding the issue on Android.