[Due for payment 2026-07-13] Company card - Not here page when open options in Setting a commercial feed

[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: v9.4.27-1
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/63205889/folder/13176706/41236836/1539813165?sort=-identifier
Email or phone of affected tester (no customers): lekima20+60307@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Win 11/Chrome
App Component: Workspace Settings

Action Performed:

1. Open https://staging.new.expensify.com
2. Navigate to Company cards in the workspace setting
3. Add a Commercial feed
4. Click on Settings
5. Click on Statement close date
6. Click back button
7. Click on Card feed name

Expected Result:

No error when click on "Statement close date" or "Card feed name"

Actual Result:

Hmm... it's not here is displayed when click on "Statement close date" or "Card feed name"

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7199195_1783154709482.Recording__2290.mp4

View all open jobs on GitHub

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

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

[melvin-bot]

Triggered auto assignment to @flodnv (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]

🔍 Investigation Summary

Classification: Frontend bug (regression)
Causing PR: #94280 — "migrate workspace company cards" by huult (High confidence)
Related issue: #95359 — same root cause (also a DeployBlockerCash from this PR)

Recommendation: REVERT #94280

The greedy getMatchingNewRoute redirect rule added by this PR rewrites the commercial-feed Settings sub-pages (Statement close date, Card feed name) into an invalid company-card-details/... path, which fails route validation and lands on the "Not here" page. A revert cleanly removes the offending rule and fixes both this issue and #95359.

📋 Root cause & evidence

The flow's routes (both static, 2 segments after company-cards):

• Statement close date → workspaces/{policyID}/company-cards/settings/statement-close-date (ROUTES.ts:2894)
• Card feed name → workspaces/{policyID}/company-cards/settings/feed-name (ROUTES.ts:2890)

The offending rule (OldRoutes.ts:82, added by #94280):

'/workspaces/*/company-cards/*/*': '/workspaces/$1/company-cards/company-card-details/$2/$3'

Mechanism: In getMatchingNewRoute, a non-trailing * matches exactly one path segment and the longest matching pattern wins. For both routes above, the segments after company-cards are exactly two (settings + statement-close-date / feed-name), so the catch-all rule matches (no more-specific rule does) and rewrites them to:

• .../company-cards/company-card-details/settings/statement-close-date
• .../company-cards/company-card-details/settings/feed-name

Those are not valid routes, so resolution falls through to SCREENS.NOT_FOUND — the "Hmm... it's not here" page. (The Settings page itself is only 1 segment — company-cards/settings — so it isn't swallowed, which is why the error only appears when you drill into a sub-page.)

The rule was intended to redirect legacy 2-segment feed/cardID details links, but it is too broad and swallows any legitimate 2-segment path under company-cards — the same defect #95359 hit via select-feed/add-card-feed.

• Reproduces on staging (contains migrate workspace company cards #94280), not production (does not yet contain it) — consistent with the PR being the cause.

Forward-fix alternative (if a revert is disruptive): drop this catch-all and rely on the more specific company-card-details/*/* rules already present at OldRoutes.ts:68-72, or constrain it so it does not match known non-legacy segments like settings.

---

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