Expensify card - Clicking edit spend rules opens Not Here page

[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: 9.4.48-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/67224492/folder/13176707/101177362/1622120592
Email or phone of affected tester (no customers): applausetester+bm882757@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Web, android
App Component: Workspace Settings

Action Performed:

Preconditions:
Collect workspace is created
Virtual Expensify card is issued

1. Go to staging.new.expensify.com
2. Navigate to the Wallet page.
3. Click on the Expensify card.
4. Click on Edit spend rules.

Expected Result:

App should navigate to the More features page if Rules is disabled, the Spend rules page or show an upgrade prompt if enabled.

Actual Result:

Not Here page appears.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7223262_1785568029953.bandicam_2026-08-01_10-03-16-370.mp4

View all open jobs on GitHub

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

[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/3480f3deb56378a6a9fc7f4fb809092064214d6780640d544188fd0491f26873

[melvin-bot]

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

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

Deploy Blocker Analysis

Root Cause: PR #95310 "Enable Rules for Collect workspaces with Control upgrade gating" (Krishna2323, merged into 9.4.48-0) added beta gating that now returns false for Collect workspaces when the account lacks the rulesRevamp beta — src/libs/PolicyUtils.ts:1644-1650:

if (isCollectPolicy(policy) && !isRulesRevampEnabled) {
    return false;
}

The Wallet → Expensify card → "Edit spend rules" entry navigates to the Spend Rules RHP, whose page wraps content in AccessOrNotFoundWrapper with featureName = ARE_RULES_ENABLED. Since arePolicyRulesEnabled now returns false for a Collect workspace without the beta, the wrapper renders the full-page "Not Here" fallback instead of the Spend Rules page / upgrade prompt. Reproducible on staging but not production, consistent with a regression from this release.

Recommended Fix: Roll forward with a targeted fix (preferred over a full revert — #95310 is broad and other checklist PRs may build on it). The Collect-without-beta path should route to the upgrade prompt / More Features experience the issue's Expected Result describes, not fall through to the NotFound fallback — either handle the disabled-feature case in navigateToSpendRulesPage (ExpensifyCardPage/index.tsx:209-214), or have the wrapper redirect to the Rules upgrade prompt for Collect policies. If a fix can't land quickly, revert #95310.

Investigation details (evidence chain, permalinks pinned to staging SHA adf7411)

1. Entry point: navigateToSpendRulesPage — ExpensifyCardPage/index.tsx:209-214 calls ROUTES.SETTINGS_WALLET_EXPENSIFY_CARD_SPEND_RULES.getRoute(...) → WalletExpensifyCardSpendRulesPage → SpendRulePageBase.
2. SpendRulePageBase.tsx:490-496 wraps content in AccessOrNotFoundWrapper with featureName = CONST.POLICY.MORE_FEATURES.ARE_RULES_ENABLED.
3. AccessOrNotFoundWrapper.tsx:138-139 & :196-202: shouldShowFullScreenFallback = !isFeatureEnabled, where isFeatureEnabled derives from isPolicyFeatureEnabledUtil(policy, ARE_RULES_ENABLED, ...). Disabled feature → "Not Here" page.
4. Regression: PolicyUtils.ts:1644-1650 (the snippet above) makes arePolicyRulesEnabled return false for a Collect workspace without the rulesRevamp beta. The issue's preconditions specify a Collect workspace.

PR attribution: production...staging shows SpendRulePageBase.tsx and AccessOrNotFoundWrapper.tsx changed this release; commits 7b1ea852d, bbcaf1470, 36aef31ef all resolve to PR #95310 (merge commit 79ccce37, merged 2026-07-31, in StagingDeployCash #97614). ExpensifyCardPage/index.tsx itself was unchanged — the break is in the shared gating util the entry point depends on.

Confidence: High — code evidence explains all symptoms (Collect precondition, staging-only, Not Here page) with a clear mechanism.

cc Krishna2323 (PR author). Keep DeployBlockerCash.

---

Next Steps: Reply with @MelvinBot implement this to create a draft PR with the targeted fix, or @MelvinBot <your feedback> to refine this analysis.