Expense-App crashes on tapping workspace distance settings.

[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): Applausetesternefits@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: Have distance rate - ₹.81 miles, set exclude a fixed distance per claim as ₹.566 miles

1. Launch app
2. Login expensifail account
3. Open workspace chat
4. Create a distance expense for waypoints
   Start - 374 wolf canyon drive
   Stop - 675 East Durant avenue
5. Open the expense
6. Tap workspace distance settings
7. Go to workspace chat - open expense
8. Tap workspace distance settings

Expected Result:

App must not crash on tapping workspace distance settings.

Actual Result:

App crashes on tapping workspace distance settings.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7231184_1786471880902.Screenrecorder-2026-08-11-23-32-57-615.mp4

logs.txt

Bug7231184_1786476479529.Screenrecorder-2026-08-12-00-54-03-757.mp4

View all open jobs on GitHub

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

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

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

https://platform.applause.com/services/links/v1/external/4344f7fc8dd7fb47f4d57f5fdaa5a23e31556b7207ce31323134b0bdd98a4eb9

[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 - "Implements the App-side slice of the workspace commuter exclusion feature" by @fedirjh (High confidence)
Related Issues: N/A

Recommendation: ROLL FORWARD

The crash is confined to one narrow new path (tapping the commuter‑exclusion system‑message link), while #93848 is a large (70‑file), beta‑gated, multi‑repo feature whose backend half (Web-Expensify#53798) is already merged — so a targeted fix by the author is safer than reverting the whole coordinated rollout. If a clean fix can't be produced quickly, fall back to reverting #93848.

Assigned: @fedirjh (PR author), @Gonals and @marufsharifi (approving reviewers) from #93848 — already auto-assigned by Melvin.
Labels: No changes. DeployBlockerCash kept (App PR caused the crash; blocks the App deploy). DeployBlocker was not present, so nothing to remove.

📋 Detailed Analysis

Evidence

• The repro string "workspace distance settings" is an exact match for the new link text introduced by [Payment due @marufsharifi] [Commuter Mileage Exclusion] [R1] Display and enforce fixed distance exclusions #93848 in src/languages/en.ts (distance.commuterExclusion.systemMessage → ...based on <a href="...">workspace distance settings</a>.).
• [Payment due @marufsharifi] [Commuter Mileage Exclusion] [R1] Display and enforce fixed distance exclusions #93848 is the only PR in the current StagingDeployCash (#98179) that implements commuter exclusions / "exclude a fixed distance per claim". It merged 2026-08-10, one day before this report.
• Reproducible on staging only, N/A in production — consistent with a brand-new feature that does not yet exist in prod. The precondition (a workspace with a fixed commuter-exclusion distance configured) is exactly what this PR adds.

Verification

• The tapped element is the new COMMUTER_EXCLUSION system report action, rendered inside the opened expense at ActionContentRouter.tsx#L481-L487 via <RenderHTML html={... getCommuterExclusionMessage(...) ...} />.
• The <a href> is built in the new getCommuterExclusionMessage at ReportActionsUtils.ts#L4788-L4805 — line 4799: workspaceDistanceSettingsLink = \${environmentURL}/${ROUTES.WORKSPACE_DISTANCE_RATES_SETTINGS.getRoute(policyID)}``.
• The link points at WORKSPACE_DISTANCE_RATES_SETTINGS, a workspace-nested RHP screen (registered under WORKSPACE_TO_RHP). Tapping routes through AnchorRenderer → openLink → Navigation.navigate(internalNewExpensifyPath) into that RHP from a report/chat context.
• All of these files are added/modified by [Payment due @marufsharifi] [Commuter Mileage Exclusion] [R1] Display and enforce fixed distance exclusions #93848 (ActionContentRouter.tsx, ReportActionsUtils.ts, ROUTES/language strings, the COMMUTER_EXCLUSION action type in CONST/index.ts and OriginalMessage.ts).

Root Cause

#93848 adds a COMMUTER_EXCLUSION system message ("Removed X commuter miles based on workspace distance settings") to the expense thread. The "workspace distance settings" text is an internal deep link to WORKSPACE_DISTANCE_RATES_SETTINGS, a workspace-nested RHP page. Tapping it navigates into that workspace RHP directly from the report context and the app crashes on Android (Redmi Note 10s / Android 13). The precise runtime frame should be confirmed from the device stack trace (Sentry), but the failure is unambiguously on this newly-introduced link/navigation path — the fix belongs in Expensify/App, not the backend.

Suggested fix direction (for the author): guard/repair navigation to the workspace RHP from the report context for this action (e.g. supply an explicit onLinkPress that goes through the proper workspace-navigation entry point, and/or beta-gate the ActionContentRouter branch behind CONST.BETAS.COMMUTER_EXCLUSIONS consistently with the settings page), or revert #93848 if a quick fix isn't available.