[Due for payment 2026-09-09] Expense-App crashes on creating workspace after creating distance expense.

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: V9.4.52-2
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: #93848
Email or phone of affected tester (no customers): Applausetesteredba@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Money Requests

Action Performed:

Pre-condition: Set exclude a fixed distance per claim to 4 miles

1. Launch app
2. Login expensifail account
3. Open workspace chat
4. Create distance expense for waypoints
   Start - India
   Stop - dehradun
5. Open the expense
6. Tap workspace distance settings link
7. Tap app top left arrow
8. Tap workspace - New - confirm

Expected Result:

App must not crash on creating workspace after creating distance expense.

Actual Result:

App crashes on creating workspace after creating distance expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7231196_1786473489793.Screenrecorder-2026-08-12-00-01-37-283.mp4

logs.txt

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7231196

Issue Owner

Current Issue Owner: @mallenexpensify

[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/1b80ecd02ba7dfd3953e0bbae50a6028f983c9c9ad9ace03f0668b9fbbfa225b

https://platform.applause.com/services/links/v1/external/c2aa6649d212e93d83abeee6a0cbf1742da2eadd2da844483e58a62482ad9272

[melvin-bot]

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

[melvin-bot]

@Gonals @marufsharifi you have been assigned to this deploy blocker because you reviewed the offending PR: #93848

[melvin-bot]

@fedirjh you have been assigned to this deploy blocker because you authored the offending PR: #93848

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

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #93848 - "[Commuter Mileage Exclusion] [R1] Display and enforce fixed distance exclusions" by @fedirjh (High confidence)
Related Issues: Feature tracked in Expensify/Expensify#642599

Recommendation: REVERT

PR #93848 is the sole origin of the "exclude a fixed distance per claim" feature that the repro's precondition depends on; the crash is only reproducible on staging and does not exist in production because the feature is brand new. Since the entire PR is dedicated to this one feature and it landed just one day before this blocker, a clean revert removes the broken code path and unblocks the staging App deploy, then the team can roll forward with a fix.

Assigned: @fedirjh (PR author), @Gonals and @marufsharifi (approving reviewers) — already assigned by melvin-bot.
Labels: No changes. DeployBlockerCash is kept (an App PR caused the crash, so the App deploy remains blocked). DeployBlocker is not present, so nothing to remove.

📋 Detailed Analysis

Evidence

• The repro precondition — "Set exclude a fixed distance per claim to 4 miles" — is the Fixed Distance commuter-exclusion setting. That entire feature (UI display + enforcement) is introduced only by PR [Payment due @marufsharifi] [Commuter Mileage Exclusion] [R1] Display and enforce fixed distance exclusions #93848 (title: "Display and enforce fixed distance exclusions").
• Reproducible in staging, N/A in production — consistent with a regression from a PR that is on staging but not yet in prod. A brand-new feature can only crash on the build that contains it.
• The bug report's BrowserStack/reference field links directly to [Payment due @marufsharifi] [Commuter Mileage Exclusion] [R1] Display and enforce fixed distance exclusions #93848, and melvin-bot auto-assigned the author and both reviewers of that PR.
• PR merged 2026-08-10, blocker filed 2026-08-11 (this deploy cycle).

Verification

The affected feature maps to files added/modified by #93848 (confirmed via gh pr view 93848 --json files):

• src/hooks/useCommuterExclusionGuard.ts (new) — guards distance flows for exclusion-enabled policies and iterates all policies.
• src/libs/DistanceRequestUtils.ts — new getTransactionCommuterExclusionData / getCommuterExclusionDisplayData / getDistanceDisplayDetailsWithCommuter.
• src/libs/actions/IOU/MoneyRequest.ts — new setMoneyRequestCommuterExclusionFields.
• src/pages/DynamicReportChangeWorkspacePage.tsx — new commuter-exclusion gating on the change-workspace flow (the "workspace" screen in the repro).
• src/components/MoneyRequestConfirmationList* and its new hooks (useDistanceRequestState, useConfirmationValidation, useTaxAmount) — the confirmation flow exercised when confirming against a workspace.

All of these are files this PR introduced or rewrote, and they sit directly on the repro path (create distance expense with an exclusion-enabled policy → open expense → change/confirm workspace).

Root Cause

The crash occurs on the commuter-exclusion code path that only #93848 adds. Static review of the new code (which is defensively written for null policies/values) did not isolate a single throwing frame, and the attached logs.txt is truncated to four [Onyx] debug lines with no JS stack trace, so the exact frame can't be pinned from the artifact alone. The failure is nonetheless contained to this PR's new commuter-exclusion logic, which runs across the policy collection and the confirmation/change-workspace flows the repro walks through:

• Policy-collection scan in the guard selector: src/hooks/useCommuterExclusionGuard.ts (lines 29-35) — runs on every POLICY collection change, including when a new workspace is created.
• Exclusion computation seeded during confirmation: src/libs/DistanceRequestUtils.ts getTransactionCommuterExclusionData (lines 340-434).
• Change-workspace gating: src/pages/DynamicReportChangeWorkspacePage.tsx (lines 105-119, 217).

@fedirjh — a full logcat / JS stack for Bug ID 7231196 would let us confirm the exact frame, but it is not required to unblock: reverting #93848 removes the feature and the crash from this staging build.