Expense - Add category button opens not here page when splitting expense in self DM

[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.3.84-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: #84382
Email or phone of affected tester (no customers): sdjsodnjiodsjsoinj1@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:

• Have a workspace.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Create an expense.
4. Open the expense.
5. Click More > Split.
6. Open any split.
7. Click Category.
8. Click Add category button.
9. Click back button on not here page.

Expected Result:

In Step 8, Add category button will open category creation page.
In Step 9, back button will return to category list.

Actual Result:

In Step 8, Add category button opens not here page when splitting expense in self DM.
In Step 9, back button on not here page closes RHP completely.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7164513_1779905210808.1.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @ZhenjaHorbach

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

[melvin-bot]

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

[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

What is the root cause of that problem?

IOURequestStepCategoryCreate.tsx is missing the policyForMovingExpenses fallback that IOURequestStepCategory.tsx already has for self-DM split edits.

When editing a split expense's category in a self-DM, the parent report has no policyID. IOURequestStepCategory.tsx:72-74 handles this correctly by falling back to policyForMovingExpenses when isEditingSplit && isSelfDM(report). But when the user clicks "Add category", navigation goes to IOURequestStepCategoryCreate, which resolves policy using only usePolicyForTransaction — no self-DM fallback. The resulting undefined policyID is passed to AccessOrNotFoundWrapper, which renders the "not found" page because isGroupPolicy(undefined) fails the PAID access check.

This was introduced by PR #84382 which added split support for unreported expenses but didn't propagate the policyForMovingExpenses fallback to the category create page.

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

In IOURequestStepCategoryCreate.tsx:

1. Import usePolicyForMovingExpenses and isSelfDM.
2. Apply the same fallback pattern used in IOURequestStepCategory.tsx: when isEditingSplit && isSelfDM(report), fall back to policyForMovingExpenses if usePolicyForTransaction returns no policy.
3. Use the effective policy's ID for policyID so AccessOrNotFoundWrapper receives a valid value.

This mirrors the existing fix in the category list page and keeps both pages consistent.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.