[Due for payment 2026-06-19] [Due for payment 2026-06-18] 'Hmm... it's not here" displayed when clicking category

[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?: 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/60093911/folder/13176721/41236966/1478231078?sort=%2Bidentifier
Email or phone of affected tester (no customers): applausetester+abrgge2t@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Android
App Component: Other

Action Performed:

1. On the device media library - Select a image and click share
2. Select share to Expensify
3. Choose option to "Submit"
4. Selec any WS or user
5. On Confirm details page > Click on category

Expected Result:

'Hmm... it's not here" should not displayed when clicking category

Actual Result:

'Hmm... it's not here" displayed when clicking category

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7177537_1781148153442.WhatsApp_Video_2026-06-11_at_05.21.46.mp4

View all open jobs on GitHub

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

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

[melvin-bot]

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

Proposal

Please re-state the problem that we are trying to solve in this issue.

In the share→Expensify flow (Android/iOS native), after selecting an image → "Submit", tapping the Category field on the Submit details page shows the "Hmm... it's not here" NotFoundView instead of opening the category selector. Regression in 9.4.5-0 staging, not reproducible in production.

What is the root cause of that problem?

PR #92161 ("migrate money request part 2") migrated MONEY_REQUEST_STEP_CATEGORY from a static route registered in the money-request navigator to a dynamic route gated by an entryScreens whitelist. That whitelist was not updated to include the share Submit Details screen.

The Category field builds its route with createDynamicRoute(...), which prepends the active route, producing:
share/submit-details/<id>/money-request/category/CREATE/SUBMIT/1/<id>

In getStateFromPath.ts, the focused route resolves to Submit_Details, which is not in the entryScreens list, so the dynamic-route guard fails, control falls through to the default React Navigation resolver, no linking pattern matches the share-prefixed money-request URL, and it returns the NOT_FOUND screen.

The whitelist that's missing the share screen is here — note SCREENS.SHARE.SUBMIT_DETAILS is absent: ROUTES.ts:221-229

Production (9.4.3-0) still uses the old static route with no entryScreens gate, which is why it only repros on staging.

Evidence chain & affected fields

• Category onPress → createDynamicRoute(DYNAMIC_ROUTES.MONEY_REQUEST_STEP_CATEGORY.getRoute(action, iouType, transactionID, reportID, reportActionID)) in CategoryField.tsx. In the share flow iouType=SUBMIT, action=CREATE, transactionID='1' (OPTIMISTIC_TRANSACTION_ID), reportID=reportOrAccountID.
• Origin screen is in a separate navigator: SCREENS.ts:1031-1036 (SUBMIT_DETAILS: 'Submit_Details') and the dedicated SHARE_MODAL_NAVIGATOR.
• The NotFoundView is returned by getStateFromPath, not by the category step page's HOC guards — those never run because the route never reaches the page.
• The same defect very likely affects the other fields migrated in migrate money request part 2 #92161 (Attendees, Accountant, Tax rate/amount, Upgrade) when reached from the share Submit screen — their entryScreens arrays also omit SCREENS.SHARE.SUBMIT_DETAILS (e.g. MONEY_REQUEST_ATTENDEE at ROUTES.ts:238-247). Worth testing each field on the Submit page.

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

Add SCREENS.SHARE.SUBMIT_DETAILS to the entryScreens array of MONEY_REQUEST_STEP_CATEGORY in src/ROUTES.ts, and do the same for every other dynamic route reachable from MoneyRequestConfirmationList that was migrated in #92161 (MONEY_REQUEST_ATTENDEE, MONEY_REQUEST_ACCOUNTANT, MONEY_REQUEST_UPGRADE, MONEY_REQUEST_STEP_TAX_RATE, MONEY_REQUEST_STEP_TAX_AMOUNT). Consider whether SCREENS.SHARE.SHARE_DETAILS (the non-Submit share/track path) needs the same treatment.

What alternative solutions did you explore?

Given this is a DeployBlockerCash, reverting #92161 is a valid fallback if the targeted entryScreens fix can't be validated quickly across all affected fields.

---

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