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
Expenses-Attendee list not visible on landscape mode during edition and "Apply" is cutted off #107498
Version Number: 9.5.43-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:#106067 Email or phone of affected tester (no customers):ibellicotest+3215@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Motorola MotoG60 / Android 12 (Hybrid app) App Component: Search
Action Performed:
Prerequisite: Account has a workspace with "Rules" and "Attendee Tracking" enabled.
Prerequisite 2: At least two expenses available.
Open the Expensify app.
Navigate to "Spend" > "Expenses"
Select more than one expense > Tap on dropdown menu > "Edit Multiple"
Tap on "Attendees"
Switch to landscape mode and tap on search input to display keyboard.
Note that "Apply" button is cutted off by keyboard.
Start typing any user´s Email on search input.
Note that results are not visible while typing without closing keyboard,
Expected Result:
"Apply" button should be completelly visible while editing attendees field in ladnscape mode, and search results should be visible while typing.
Actual Result:
"Apply" button is cutted off by keyboard during "Attendees" field edition while in landscape mode, and search results are not visible while typing if keyboard is not dismissed.
👋 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.
Confidence: High in the introducing PR; medium in the exact clipping mechanism. The likely cause is insufficient space above the landscape keyboard for the picker’s header, search results, and non-shrinking Apply footer.
The merge preceded the reported 9.5.43-0 release. No intervening changes to the relevant picker/layout files were found between merge and release.
The shared picker predates this PR: this may be a latent shared-layout defect newly exposed in bulk editing, rather than a newly introduced keyboard calculation.
What changes do you think we should make in order to solve the problem?
Recommend reverting the introducing PR as the conservative deploy-unblocking option and retaining DeployBlockerCash. A targeted layout fix has not been validated sufficiently to recommend rolling forward instead.
For a roll-forward, first verify that search results remain visible and scrollable and Apply remains fully reachable in Android hybrid landscape with the keyboard open. Check rotation and the shared single-expense attendee picker too.
What alternative solutions did you explore? (Optional)
Restoring only the previous full-page bulk attendee editor would reduce scope compared with a complete revert. Fixing the shared sheet’s available-height handling could preserve the new UI, but requires native verification.
Verification limitation: No runtime tests were performed. This invocation permits web testing only; web evidence would not establish Android hybrid keyboard behavior. No code or issue metadata was changed.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/107498) to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
Activity
applause-bot commentedon Nov 20, 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/32bd98b1872f1daeec55d361bdd432accf894eee9d96727038dad81e69bead84
expensify-chore-bot commentedon Nov 20, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #106067
expensify-chore-bot commentedon Nov 20, 2026
@mountiny @ikevin127 you have been assigned to this deploy blocker because you reviewed the offending PR: #106067
expensify-chore-bot commentedon Nov 20, 2026
@DylanDylann you have been assigned to this deploy blocker because you authored the offending PR: #106067
expensify-chore-bot commentedon Nov 20, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 20, 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:
MelvinBot commentedon Nov 20, 2026
Proposal
What is the root cause of that problem?
The affected flow was introduced by [CFI] Update the Edit multiple flow to use inline editing and dropdown down style rows. It replaced the full-page bulk attendee editor with a shared picker that uses a bottom sheet on native devices.
Confidence: High in the introducing PR; medium in the exact clipping mechanism. The likely cause is insufficient space above the landscape keyboard for the picker’s header, search results, and non-shrinking Apply footer.
Code and release evidence
What changes do you think we should make in order to solve the problem?
Recommend reverting the introducing PR as the conservative deploy-unblocking option and retaining
DeployBlockerCash. A targeted layout fix has not been validated sufficiently to recommend rolling forward instead.For a roll-forward, first verify that search results remain visible and scrollable and Apply remains fully reachable in Android hybrid landscape with the keyboard open. Check rotation and the shared single-expense attendee picker too.
What alternative solutions did you explore? (Optional)
Restoring only the previous full-page bulk attendee editor would reduce scope compared with a complete revert. Fixing the shared sheet’s available-height handling could preserve the new UI, but requires native verification.
Verification limitation: No runtime tests were performed. This invocation permits web testing only; web evidence would not establish Android hybrid keyboard behavior. No code or issue metadata was changed.
Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/107498)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
view run
mountiny commentedon Nov 20, 2026
We should fix this but I think its too narrow of an edge case and they can change to portrait to process this