[HOLD for payment 2024-06-11] [HOLD for payment 2024-06-06] IOU - Save button is not above keyboard when waypoint input is in focus

[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: 1.4.77-0
Reproducible in staging?: Y
**Reproducible in production?:**N
If this was caught during regression testing, add the test name, ID and link from TestRail: #42464
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Recent destinations list has a few addresses

1. Go to staging.new.expensify.com
2. Go offline
3. Go to FAB > Submit expense > Distance
4. Tap Start
5. Tap on the input
6. Note that Save button does not appear above the keyboard
7. Tap system back button (or swipe) to dismiss the keyboard while the input is still in focus

Expected Result:

In Step 5, Save button will appear above the keyboard (production behavior)
In Step 7, Save button will appear at the bottom when keyboard is dismissed and input is still in focused

Actual Result:

In Step 5, Save button does not appear above the keyboard (production behavior)
In Step 7, Save button is missing at the bottom when keyboard is dismissed and input is still in focused

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6495019_1716981635722.Screen_Recording_20240529_191531_New_Expensify.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @trjExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

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

[lanitochka17]

@trjExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1