You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-10-21] Android - Expense - Category list is hidden behind the keyboard when search field is focused #103129
Version Number: 9.5.3-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:#102665 Email or phone of affected tester (no customers):jsoidjndoiniodnsjojd@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:
Precondition:
Enable anchoredFieldDropdowns
Launch Expensify app.
Open FAB > Create expense > Manual.
Tap Category.
Tap search field.
Expected Result:
Category list will move above the keyboard.
Actual Result:
Category list is hidden behind the keyboard when search field is focused.
👋 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:
Identify the pull request that introduced this issue and revert it.
Root cause: On phones, CategoryPickerModal opens as a sheet docked to the bottom of the screen. It never passes avoidKeyboard, so the keyboard covers the list when the search field gets focus (CategoryPickerModal.tsx:97-112).
Recommendation: fix forward, don't revert. Pass avoidKeyboard to PopoverWithMeasuredContent in CategoryPickerModal. The other bottom sheets with search already do this. For example, PopoverMenu uses avoidKeyboard={isSearchEnabled}. The bug only appears with the anchoredFieldDropdowns beta on, and production isn't affected. Demoting it from deploy blocker seems reasonable. Reverting would back out a 17-file feature over one missing prop.
Investigation details
Why this PR
The PR added the anchoredFieldDropdowns beta and the new ExpenseFieldDropdown and CategoryFieldDropdown components. This flow didn't exist before it, which matches "N/A in production."
Before this PR, CategoryPickerModal was only used by the Search table's inline-edit cell. This PR is the first to show it as a bottom sheet on phones.
How it breaks
On a phone, ExpenseFieldDropdown opens CategoryFieldDropdown, which renders CategoryPickerModal at a fixed height (POPOVER_DROPDOWN_MAX_HEIGHT, 416).
ReanimatedModal wraps its content in a KeyboardAvoidingView only when avoidKeyboard is true. The prop defaults to false (ReanimatedModal/index.tsx:36, :250).
CategoryPickerModal auto-focuses the search input (shouldAutoFocusSearchInput) but doesn't pass avoidKeyboard. The sheet stays at the bottom and the keyboard hides it.
Things to check with the fix
On small Android phones, the fixed 416 height plus the keyboard may run off the top of the screen. You may also need to cap the height while the keyboard is open.
The iOS modal also passes avoidKeyboard through, so iOS likely has the same bug, even though only Android was reported.
Caveats: I found this by reading the code and didn't reproduce it on a device. I didn't scan every other PR in the staging checklist. Since only this PR changed these files, another cause is unlikely.
changed the title [-]Android - Expense - Category list is hidden behind the keyboard when search field is focused[/-][+][Due for payment 2026-10-21] Android - Expense - Category list is hidden behind the keyboard when search field is focused[/+]on Oct 14, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.8-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-21. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
applause-bot commentedon Oct 6, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/d0441d8ace35d40c4db49968158f0bf700e0036da3017293b308dd6428c82080
melvin-bot commentedon Oct 6, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #102665
github-actions commentedon Oct 6, 2026
👋 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:
melvin-bot commentedon Oct 6, 2026
@puneetlath @ikevin127 you have been assigned to this deploy blocker because you reviewed the offending PR: #102665
melvin-bot commentedon Oct 6, 2026
@DylanDylann you have been assigned to this deploy blocker because you authored the offending PR: #102665
melvin-bot commentedon Oct 6, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Oct 6, 2026
🤖 Deploy Blocker Investigation
Causing PR: [CFI] Open the Category list in a container anchored to its row (
Expensify/App#102665). The bot assigned the right PR. Confidence: high.Root cause: On phones,
CategoryPickerModalopens as a sheet docked to the bottom of the screen. It never passesavoidKeyboard, so the keyboard covers the list when the search field gets focus (CategoryPickerModal.tsx:97-112).Recommendation: fix forward, don't revert. Pass
avoidKeyboardtoPopoverWithMeasuredContentinCategoryPickerModal. The other bottom sheets with search already do this. For example,PopoverMenuusesavoidKeyboard={isSearchEnabled}. The bug only appears with theanchoredFieldDropdownsbeta on, and production isn't affected. Demoting it from deploy blocker seems reasonable. Reverting would back out a 17-file feature over one missing prop.Investigation details
Why this PR
anchoredFieldDropdownsbeta and the newExpenseFieldDropdownandCategoryFieldDropdowncomponents. This flow didn't exist before it, which matches "N/A in production."CategoryPickerModalwas only used by the Search table's inline-edit cell. This PR is the first to show it as a bottom sheet on phones.How it breaks
ExpenseFieldDropdownopensCategoryFieldDropdown, which rendersCategoryPickerModalat a fixed height (POPOVER_DROPDOWN_MAX_HEIGHT, 416).PopoverWithMeasuredContentrenders aBOTTOM_DOCKEDmodal (PopoverWithMeasuredContent/index.tsx:36-47).ReanimatedModalwraps its content in aKeyboardAvoidingViewonly whenavoidKeyboardis true. The prop defaults tofalse(ReanimatedModal/index.tsx:36,:250).CategoryPickerModalauto-focuses the search input (shouldAutoFocusSearchInput) but doesn't passavoidKeyboard. The sheet stays at the bottom and the keyboard hides it.Things to check with the fix
avoidKeyboardthrough, so iOS likely has the same bug, even though only Android was reported.Caveats: I found this by reading the code and didn't reproduce it on a device. I didn't scan every other PR in the staging checklist. Since only this PR changed these files, another cause is unlikely.
view run
1 remaining item
trjExpensify commentedon Oct 6, 2026
behind a beta, demoting.
melvin-bot commentedon Oct 13, 2026
@DylanDylann Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
[-]Android - Expense - Category list is hidden behind the keyboard when search field is focused[/-][+][Due for payment 2026-10-21] Android - Expense - Category list is hidden behind the keyboard when search field is focused[/+]melvin-bot commentedon Oct 14, 2026
@ikevin127 / @DylanDylann
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.8-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-21. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Oct 15, 2026
@ikevin127 Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!
ikevin127 commentedon Oct 16, 2026
Note
This one can be closed, no payment needed here as it was a regression coming from this main issue's PR.