[Due for payment 2026-06-19] [Due for payment 2026-06-18] Expense - Category, Tax and Attendees field open not here page

[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.5-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: #92161
Email or phone of affected tester (no customers): iosjnnsjdosnjsodj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Run Onyx.merge('betas', ['newManualExpenseFlow']); in console.
• Enable Taxes and Rules.
• Enable Attendee tracking in Rules settings.

1. Go to staging.new.expensify.com
2. Open FAB > Create expense > Manual.
3. Open Category.
4. Close not here page.
5. Open Tax field.
6. Close not here page.
7. Open Attendees page.

Expected Result:

Category, Tax and Attendees field will open the correct page.

Actual Result:

Category, Tax and Attendees field open not here page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7177545_1781148719582.16.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7177545

[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/8bef857e615531266283e2174b0562a7da3454fe6ea085c37dd89662441d77f0

[melvin-bot]

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

[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

Root Cause: PR #92161 migrated Category / Tax / Attendees (and Accountant / Upgrade) to the new dynamic-suffix routing system, but the entryScreens allow-lists for those dynamic routes are missing the screen the new manual flow actually runs on.

In newManualExpenseFlow, IOURequestStartPage renders the confirmation fields inline, so the focused React Navigation screen stays SCREENS.MONEY_REQUEST.CREATE (Money_Request_Create) — not STEP_CONFIRMATION. When a field is tapped, createDynamicRoute appends the dynamic suffix to the current path, and the resolver validates the focused screen against entryScreens:

Why it lands on the "not here" page

The entry-screen guard at getStateFromPath.ts:44 only proceeds if the focused route name is in the route's entryScreens. The four affected routes list only STEP_CONFIRMATION (+ REPORT / RIGHT_MODAL variants) and not MONEY_REQUEST.CREATE:

• MONEY_REQUEST_STEP_TAX_RATE — ROUTES.ts:183
• MONEY_REQUEST_STEP_TAX_AMOUNT — ROUTES.ts:201
• MONEY_REQUEST_STEP_CATEGORY — ROUTES.ts:219
• MONEY_REQUEST_ATTENDEE — ROUTES.ts:238

Because every candidate fails validation, resolution falls through to RNGetStateFromPath at line 70, which has no static route for the combined …/start/…/category/… path and returns the NotFoundPage. (A [DynamicRoute] None of the … candidate(s) passed entryScreens validation warning is logged at the moment of failure — useful to confirm in logs.)

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

Add SCREENS.MONEY_REQUEST.CREATE to the entryScreens arrays of the affected dynamic routes in src/ROUTES.ts: MONEY_REQUEST_STEP_CATEGORY, MONEY_REQUEST_STEP_TAX_RATE, MONEY_REQUEST_STEP_TAX_AMOUNT, and MONEY_REQUEST_ATTENDEE.

Also audit MONEY_REQUEST_ACCOUNTANT (ROUTES.ts:256) and MONEY_REQUEST_UPGRADE (ROUTES.ts:275) — they were part of the same migration and reachable from the embedded confirmation, so they likely need the same entry. (MONEY_REQUEST_UPGRADE already lists HOME/INBOX/SEARCH.ROOT but still not CREATE.)

What alternative solutions did you explore? (Optional)

Reverting #92161 would also unblock the deploy, but the targeted entryScreens fix is much smaller and preserves the migration.

---

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