mWeb - Workspace - "Confirm" button is overlapped by keyboard during WS creation

[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: 9.0.88-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): ibellicotest+191@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the staging.new.expensify.com website
2. Tap on "Settings" and select "Workspaces"
3. Tap on "New Workspace"
4. During confirmation process, check "Confirm" button behaviour when keyboard is opened

Expected Result:

"Confirm" button during workspace creation process should be displayed above the keyboard

Actual Result:

"Confirm" button, during workspace creation process, is displayed cutted off by the keyboard

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6720050_1737477730457.Confirm.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @amyevans (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[allgandalf]

c.c. @Krishna2323 for vizz

[amyevans]

This is a relatively minor UI issue which doesn't warrant blocking deploy

[amyevans]

#53845 is the feature where this was introduced - @Krishna2323 are you able to tackle a fix here?

[Krishna2323]

@allgandalf, I think this is same as #53692, can this be handled there?