Expense - Nothing happens after clicking Create report when there is no workspace

[vincdargento]

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

Action Performed:

Precondition:

• Account has no workspace.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Create an expense.
4. Open the expense.
5. Click More > Move to report.
6. Click Create report.

Expected Result:

Upgrade page will open.

Actual Result:

Nothing happens after clicking Create report when there is no workspace.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #84512 - "Feat: Add 'Move to report' in the 'More' menu of a one-expense report" by @nyomanjyotisa (High confidence)
Related Issues: #83884 (original feature request)

Recommendation: REVERT

PR #84512 introduced a new "Move to report" feature but failed to handle the scenario where a user has no workspace. The bug prevents users from upgrading to a workspace when moving expenses, blocking a critical user flow.

Labels: Keeping DeployBlockerCash (frontend bug - App deploy blocked). This label should not be removed as the fix requires changes to the App repository.

📋 Detailed Analysis

Evidence

The issue occurs in the new flow added by PR #84512:

1. User clicks "Move to report" (new option added by PR Feat: Add 'Move to report' in the 'More' menu of a one-expense report #84512)
2. This navigates to MONEY_REQUEST_EDIT_REPORT route (new route/page added by PR Feat: Add 'Move to report' in the 'More' menu of a one-expense report #84512)
3. On that page, "Create report" button appears
4. Clicking it does nothing when user has no workspace

Verification

Affected files modified by PR #84512:

• /home/runner/_work/App/App/src/pages/iou/request/step/IOURequestEditReport.tsx (new file)
• /home/runner/_work/App/App/src/components/MoneyReportHeader.tsx (adds "Move to report" option)
• /home/runner/_work/App/App/src/components/MoneyRequestHeader.tsx (adds "Move to report" option)
• /home/runner/_work/App/App/src/libs/ReportSecondaryActionUtils.ts (adds logic for showing the option)

The bug is in the new IOURequestEditReport.tsx file, specifically the createReport function (lines 132-149).

Root Cause

In IOURequestEditReport.tsx, the createReport function has this logic:

const createReport = () => {
    if (hasPerDiemTransactions) {
        handleCreateReport();
        return;
    }
    if (!hasPerDiemTransactions && !policyForMovingExpensesID && !shouldSelectPolicy) {
        return;  // ← EXITS EARLY, DOES NOTHING
    }
    if (shouldSelectPolicy) {
        Navigation.navigate(ROUTES.NEW_REPORT_WORKSPACE_SELECTION.getRoute(true, backTo));
        return;
    }
    // ... rest of function
};

When a user has no workspace, the hook usePolicyForMovingExpenses returns:

• policyForMovingExpensesID = undefined
• shouldSelectPolicy = false (line 81 of usePolicyForMovingExpenses.ts)

This causes the function to return early on line 138, doing absolutely nothing when clicked.

Expected behavior: When a user has no workspace, clicking "Create report" should either:

1. Navigate to an upgrade/workspace creation flow (as indicated by "Upgrade page will open" in the issue)
2. Navigate to workspace selection (like the regular expense creation flow does)

What happens: The function exits early and nothing happens, leaving the user stuck.

The root cause is that usePolicyForMovingExpenses.ts line 81 returns shouldSelectPolicy: false when the user has zero workspaces, but the createReport function expects shouldSelectPolicy: true to trigger the upgrade/selection flow.

Fix location: The logic in IOURequestEditReport.tsx line 137 needs to handle the no-workspace case, OR usePolicyForMovingExpenses.ts line 81 should return shouldSelectPolicy: true when the user has zero workspaces (to match user expectations for creating a workspace).

[vincdargento]

This issue was reproduced in the snapshot build of PR #84452, but makes sense that the culprit PR is #84512