[Due for payment 2026-07-02] "Enter" Key does not work in "Exclude a fixed distance per claim"

[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.17-0
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: #92496
Email or phone of affected tester (no customers): applausetester+en@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Macbook Pro 2023 / Tahoe 26.4.1
App Component: Workspace Settings

Action Performed:

1. Access staging.new.expensify.com and sign into beta user
2. Go to WS > Distance Rates > Setting > Exclude Commutes choose "Exclude a fixed distance per claim" and set a distance.
3. Tap Enter on Keyboard

Expected Result:

Value is entered

Actual Result:

Nothing happnes

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7188126_1782174857429.User_cant_tap_Enter.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7188126

[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/f9aec82546a98d2767e85c6835e8889463dee17472e202122fdc563588c57f49

[melvin-bot]

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

[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

Please re-state the problem that we are trying to solve in this issue.

On WS → Distance Rates → Settings → Exclude Commutes, when you choose "Exclude a fixed distance per claim", type a distance, and press Enter, nothing happens. The value should be submitted (same as tapping Save).

What is the root cause of that problem?

The new PolicyCommuterExclusionsPage (added in #92496) never wires the Enter key to a submit action:

• The Save button in the FixedFooter has no pressOnEnter prop, so it doesn't listen for the Enter keyboard shortcut.
• The fixed-distance TextInput has no onSubmitEditing handler.

Because the page uses a plain TextInput + standalone Button (not a FormProvider, which would handle Enter automatically), there is no code path connecting the Enter key to onSave. Pressing Enter is a no-op by omission.

Code references

• Save button without pressOnEnter: src/pages/workspace/distanceRates/PolicyCommuterExclusionsPage.tsx:191-196
• TextInput without onSubmitEditing: src/pages/workspace/distanceRates/PolicyCommuterExclusionsPage.tsx:114-129
• Button supports pressOnEnter (triggers onPress on Enter): src/components/Button/index.tsx:100
• Reference pattern used elsewhere — pressOnEnter on a footer Save button: src/pages/workspace/companyCards/assignCard/TransactionStartDateStep.tsx:134

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

Add pressOnEnter to the Save button so the Enter key triggers onSave (the same handler that validates the input and saves):

 <Button
     success
     large
+    pressOnEnter
     text={translate('common.save')}
     onPress={onSave}
 />

This matches the established convention across other workspace settings pages (e.g. TransactionStartDateStep, WorkspaceCompanyCardEditTransactionStartDatePage). onSave already handles validation (distanceMustBePositive) and the disabled-method/no-change cases, so routing Enter through it is safe.

Alternative considered

Adding onSubmitEditing={onSave} to the TextInput would also work, but pressOnEnter on the Save button is the more consistent codebase pattern and also covers the case where focus is on the selection list rather than the input.

Confidence: High

The fix is local to the App repo (frontend only) and matches an existing, widely-used pattern.

---

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

[chiragsalian]

Behind a beta, not a blocker. Reassigning to alberto since he's working on it.