[Due for payment 2026-06-25] [$250] Android - Save button on Pronouns page is hidden by device navigation bar

[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.4.8-2
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: #92749
Email or phone of affected tester (no customers): jsodinjosdjsoinjsiojs@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: User Settings

Action Performed:

Precondition:

• Set device navigation to bar instead of gestures.

1. Launch Expensify app.
2. Go to Account > Profile > Pronouns.
3. Dismiss the keyboard.

Expected Result:

Save button on Pronouns page will be above device navigation bar.

Actual Result:

Save button on Pronouns page is hidden by device navigation bar.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

View all open jobs on GitHub

Applause Internal Information
Exported by: Nathan Lemma
Bug ID: 7182672

Issue Owner

Current Issue Owner: @truph01

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022067176868707005651
• Upwork Job ID: 2067176868707005651
• Last Price Increase: 2026-06-17

[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/5ad090765a77915c55a586bbcc0d4679489ac273ca270c33eccaaaf537488886

[melvin-bot]

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

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

PR #92749 added a Save button to the Pronouns page via confirmButtonOptions on SelectionList. That button renders inside a FixedFooter, and FixedFooter only adds bottom safe-area padding when it receives addBottomSafeAreaPadding.

On the Pronouns page neither source of bottom padding is present:

• The ScreenWrapper uses includeSafeAreaPaddingBottom={false}.
• The SelectionList does not pass addBottomSafeAreaPadding, which defaults to false.

With no bottom safe-area padding from either side, the Save button sits flush against the bottom edge and is covered by the Android 3-button navigation bar.

The sibling page changed in the same PR — RulesReimbursableDefaultPage — correctly passes addBottomSafeAreaPadding, which is why only Pronouns is affected.

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

Pass addBottomSafeAreaPadding to the SelectionList in PronounsPage.tsx, matching what RulesReimbursableDefaultPage already does. This routes the safe-area padding through FixedFooter so the Save button clears the navigation bar, while keeping includeSafeAreaPaddingBottom={false} on the ScreenWrapper (needed so the search input/keyboard behavior is unaffected).

Confidence & verification notes

• Confidence: High. Code path is fully traced: confirmButtonOptions → Footer → FixedFooter(addBottomSafeAreaPadding).
• The bug is Android-only (matches the report) because the missing padding is the device navigation-bar inset.
• Alternative considered: setting includeSafeAreaPaddingBottom back to true on the ScreenWrapper. Rejected — addBottomSafeAreaPadding on the list is the established pattern for SelectionList footers and is what the sibling page in the same PR uses, so it is the minimal, consistent fix.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/93738) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[lakchote]

coming from #92749 @truph01

Can you raise a fix?