Status-Message box hidden behind save button, Pronouns search box is partially hidden

[lanitochka17]

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-3
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. Go to settings - profile
3. Turn landscape
4. Tap status
5. Keep cursor on Message box

bug2:

1. Launch app
2. Go to settings - profile
3. Turn landscape
4. Tap Pronouns
5. Keep cursor on Pronouns box

Expected Result:

In status, message box must not be hidden behind save button.
Pronouns search box must not be partially hidden.

Actual Result:

In status, message box hidden behind save button.
Pronouns search box is partially hidden.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7125099_1775671325399.Screenrecorder-2026-04-08-23-28-55-496.mp4

Bug7125099_1775673338825.screenrecorder-2026-04-08-23-39-28-871.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @rushatgabhane

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