[Due for payment 2026-04-23] Reports - No unreported expenses page doesn't fit on landscape and doesn't scroll

[jponikarchuk]

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.54-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: #85229 and https://test-management.browserstack.com/projects/2219752/folder/13176730/test-cases/41237114
Email or phone of affected tester (no customers): gatantm+6320@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: iPhone 12.mini, iOS 16.7
App Component: Money Requests

Action Performed:

1. Launch the app and login with any account being on landscape mode
2. Tap on FAB and tap Create report
3. Tap on Add expenses
4. Select Add unreported expenses (if there are unreported expenses add all and repeat this step)

Expected Result:

The page fits the screen without overlap

Actual Result:

The page doesn't fit the screen with the CTA been overlapped by the home bar but there's no scrolling on it

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022041776340659917259
• Upwork Job ID: 2041776340659917259
• Last Price Increase: 2026-04-08

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #85229

[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.