Repository navigation
[Due for payment 2026-10-21] [Exploratory] Expense-Amount/merchant row hidden behind keypad in expense creation page #102082
Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: V9.4.92
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #100886
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Money Requests
Action Performed:
- Launch app
- Tap create expense
- Turn to landscape
- Try to focus on amount or merchant row
Expected Result:
Amount/merchant row must not be hidden behind keypad in expense creation page
Actual Result:
Amount/merchant row hidden behind keypad in expense creation page
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7267161_1790163212215.Screenrecorder-2026-09-23-16-59-20-955.mp4
Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7267161
Issue Owner
Current Issue Owner: @mallenexpensifyMetadata
Metadata
Type
Projects
- Status
Activity
applause-bot commentedon Sep 23, 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/188998a3c17d53361deacf6a5a1c7f269ff139a2f77457f32fc0b390b0dcec77
truph01 commentedon Sep 27, 2026
cc @GCyganek since it belongs to the landscape project #77280
GCyganek commentedon Sep 28, 2026
@MelvinBot assign me and @truph01
MelvinBot commentedon Sep 28, 2026
Done. I assigned
GCyganekandtruph01to this issue.view run
melvin-bot commentedon Oct 12, 2026
Triggered auto assignment to @NicolasBonet, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
NicolasBonet commentedon Oct 12, 2026
Could you check this with the latest merge? @GCyganek
17 remaining items
truph01 commentedon Oct 20, 2026
@NicolasBonet Could you check my price increase request #102082 (comment)?
truph01 commentedon Oct 20, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR:
Link to the comment on the Issue:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Test:
1. Create expense
2. Spend screen
3. Wallet
4. Workspace remove fixed distance
commuterExclusionsbeta enabled5. Workspace additional approver
6. Workspace company card edit name
Pre-condition: Keep font size to maximum
Do we agree 👍 or 👎
melvin-bot commentedon Oct 20, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 20, 2026
Payment Summary
Resolving PRs:
Fix elements hidden behind keyboard in landscape mode #102433
Contributor: @GCyganek does not require payment (Contractor)
Reviewer: @truph01 owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Oct 21, 2026
Payment Summary
Contributor+: @truph01 due $525 via NewDot
NicolasBonet commentedon Oct 22, 2026
@mallenexpensify they are requesting an increase of 3x as there were tackling 6 issues with this, all of them were related and this is itself a regression of a previously reverted PR, I do think that testing and validating is worth extra so perhaps we can indeed do a 2x or 3x increase for this one? Not sure if this been a regression could invalidate that.
mallenexpensify commentedon Oct 22, 2026
Thanks @NicolasBonet, I'm on the fence but going with 3x. This issue is an edge case. We don't often pay more when one PR fixed multiple issues, the difference here is that there was planning and work done before the PR was merged to address the different issues. Price updated above.