Expense-Delete and cancel button partially hidden behind navigation bar in delete modal.

[nlemma]

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: V9.3.54
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): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Workspace Settings

Action Performed:

1. Launch app
2. Open workspace chat
3. Create a Manual distance expense with receipt capturing an image
4. Open the expense
5. Open the receipt
6. Turn to landscape mode
7. Tap Dots - delete
8. In delete confirmation modal box, delete and cancel button partially hidden behind navigation bar

Expected Result:

In landscape mode, Delete and cancel button must not be partially hidden behind navigation bar in delete modal.

Actual Result:

In landscape mode, Delete and cancel button partially hidden behind navigation bar in delete modal.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7124558_1775637601462.Screenrecorder-2026-04-08-14-04-29-568.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @GCyganek

[melvin-bot]

@mjasikowski recently merged #85229, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @AndrewGable (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.