[$250] Expenses - Scan and manual expenses are not moved to a new report

[jponikarchuk]

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.2.28-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: #70240
Email or phone of affected tester (no customers): agexptest+pr0810.5@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 11/ Chrome, Samsung S23FE/ Android 15, iPhone 13 Mini/ iOS 18.5
App Component: Money Requests

Action Performed:

Preconditions:
Create a new account with a Gmail address (pick "Track and budget expenses" in the intent selector).
Have one workspace.
Personal policy auto reporting is off + Group policy auto reporting is off

1. Go to staging.new.expensify.com
2. Click FAB > Create expense > Manual
3. Verify the Report field is set to None
4. Create expense
5. Verify the expense is created in your self DM report
6. In self DM, click Submit it to someone
7. Select the workspace and create the expense
8. Repeat steps 2-7, but in step 2, choose Scan

Expected Result:

The expenses are added to a new report, and both are accessible through workspace chat.

Actual Result:

For manual expense, infinite loading occurs after step 8 when accessing the report thread.
For scan expense, the new report is empty. Sometimes the scan expense is moved successfully.
After reset and refresh, the expenses appear back in the self DM.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

11.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021977965289126600192
• Upwork Job ID: 1977965289126600192
• Last Price Increase: 2025-10-28
• Automatic offers:
• situchan | Contributor | 109315866

Issue Owner

Current Issue Owner: @

[melvin-bot]

Triggered auto assignment to @clarajones-expensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @mollfpr (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.

[mollfpr]

@s77rt Could you check this issue? It's coming from #70240