Move expenses - Members expenses are not moved anywhere

[lanitochka17]

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.2.36-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #72715
Issue reported by: Applause - Internal Team

Action Performed:

Preconditions:
Admin invites member to two workspaces
Member has created an expense in both workspace chats

1. As the Admin, navigate to Reports/ Expenses
2. Select both expenses via checkbox
3. Click "2 selected" - Move expenses - Create report
4. Open the default workspace chat, where the report must have been created, open the report
5. Repeat steps 1-3, select the existing report
6. Check the report in the workspace chat

Expected Result:

The expenses were moved to the report, created in the Admin's workspace chat

Actual Result:

The report was created in the Admin's workspace chat, but the expenses were not moved a anywhere

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6981844_1761166361984.Expenses_not_moved.mp4

View all open jobs on GitHub

[melvin-bot]

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

[blimpich]

Hmm. We already reverted #72715, which is the PR linked in the issue description. So I'm not sure what this is.

[blimpich]

Issue description says this is reproducible in production, therefore not a deploy blocker