Spend - Extra space below Confirm button when keyboard is opened

[applause-bot]

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.82-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #90029
Email or phone of affected tester (no customers): sdjsodnjiodsjsoinj1@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:

1. Launch Expensify app.
2. Go to Spend > Expenses.
3. Tap Filters.
4. Tap Amount.
5. Focus on input field if not focused.

Expected Result:

There will be no extra space below Confirm button when keyboard is opened.

Actual Result:

Extra space is shown below Confirm button when keyboard is opened.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7163076_1779755093457.Screen_Recording_20260526_082300_Expensify.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7163076

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/4577a69826680a1c1b00413b2765117bf78f7008cfc899d085bee7a295d3d4da

https://platform.applause.com/services/links/v1/external/d5bee4e98d7285ef73d0d28ffa88bfe496d98c9f4af89bc396cea28aaf698ff7

[melvin-bot]

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

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

[MelvinBot]

Proposal

What is the root cause of that problem?

AdvancedFiltersFullscreen passes includeSafeAreaPaddingBottom to ScreenWrapperContainer unconditionally. This causes ScreenWrapperContainer to always render an empty bottom <View> with safe area padding (~34px on notched iPhones). When a filter like Amount is selected, the Confirm button already has its own pb5 (20px padding). When the keyboard opens, the modal shrinks available space but that bottom safe area padding remains fixed, creating visible extra space below the Confirm button.

What changes do you think we should make in order to solve the problem?

In AdvancedFiltersFullscreen.tsx:43, make includeSafeAreaPaddingBottom conditional on whether a filter is selected:

includeSafeAreaPaddingBottom={!selectedFilter}

The safe area padding is needed for the filter list view (which shows the Apply Filters / Reset buttons at the bottom), but not for individual filter content views like Amount that handle their own bottom spacing via the Confirm button's pb5.

What alternative solutions did you explore? (Optional)

Alternatively, we could remove pb5 from the Confirm button in AmountFilterComponent when in fullscreen mode and rely solely on the safe area padding. However, this is less clean because it couples the filter component's styling to the container's safe area behavior, and the same issue could affect other filter content views that have their own bottom padding.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.