[$250] Distance rates - Save button is not at the bottom of RHP on Add rate page

[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.79-1
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: #90153
Email or phone of affected tester (no customers): applausetester+khcategory19@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Log in with Expensifail account.
• Enable Distance rates in workspace settings.

1. Go to staging.new.expensify.com
2. Go to workspace settings > Distance rates.
3. Click Add rate.

Expected Result:

Save button will be at the bottom of RHP.

Actual Result:

Save button is not at the bottom of RHP on Add rate page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7160123_1779402030115.6.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @Krishna2323

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022057601350114653554
• Upwork Job ID: 2057601350114653554
• Last Price Increase: 2026-05-21

[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/8e7ee7a478f35cb4b83b87043fc6be475f5458443a8c6451a28799d0d6c48bb7

[melvin-bot]

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

[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 #90153 added a date-bound mileage rate creation flow to CreateDistanceRatePage.tsx. When the isDateBoundMileageRateEnabled beta is active, the form renders four View-wrapped inputs (name, rate, startDate, endDate) that only occupy their natural height. Combined with submitFlexEnabled={false}, nothing fills the remaining vertical space, so the Save button sits directly below the last input instead of at the bottom of the RHP.

In the non-beta path, AmountForm renders NumberWithSymbolForm which has an internal flex:1 container that naturally fills available space and pushes the button down.

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

In CreateDistanceRatePage.tsx, set submitFlexEnabled to true when the date-bound beta is enabled. This gives the submit button container flex:1 via FormWrapper.tsx, pushing the Save button to the bottom of the RHP. The non-beta path can keep submitFlexEnabled={false} since AmountForm already handles spacing internally.

Change line 121 from:
submitFlexEnabled={false} to submitFlexEnabled={!isDateBoundMileageRateEnabled}

What alternative solutions did you explore? (Optional)

Wrapping the date-bound inputs in a <View style={styles.flexGrow1}> would also work, but toggling submitFlexEnabled is simpler and uses the existing FormWrapper mechanism designed for exactly this purpose.

---

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.

[neil-marcellini]

I think this is not a deploy blocker because it's only happening under the beta. I'll test and verify on dev.

@Krishna2323 pls work on the fix, you can use Melvin if you want.

[neil-marcellini]

Yep, when the beta is enabled it matches staging exactly so not a blocker.

2026-05-21_16-14-37.mp4