Android - Radio buttons are hidden behind navigation bar, unable to scroll down filters

[mitarachim]

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
Email or phone of affected tester (no customers): jsdjosidjiojisojio3@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: Search

Action Performed:

Precondition:

• Set device navigation to navigation bar instead of gestures.

1. Launch Expensify app in landscape mode.
2. Go to Reports > Expenses.
3. Tap Type quick filter and scroll down.
4. Close the modal.
5. Tap Status quick filter and scroll down.

Expected Result:

• Radio buttons will not be hidden behind navigation bar.
• Filter modal can be scrolled down to reveal Apply and Reset button.

Actual Result:

• Radio buttons are hidden behind navigation bar.
• Filter modal cannot be scrolled down to reveal Apply and Reset button.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7124265_1775609100773.08.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @GCyganek

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