[HOLD retest when 63202 is deployed] Expense Report - Admin gets error changing WS on duplicated submitted expenses by member

[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.1.60-1
**Reproducible in staging?:**Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

Pre-requisite: Expensifail user has a two workspaces, one includes a member

1. Go to https://staging.new.expensify.com/
2. Log in with an Expensifail account
3. Create a WS and invite a member (another Expensifail user)
4. Open an incognito tab, log in with the member’s account
5. As the member, create an expense report in the WS
6. Within the report, create two duplicate expenses and submit the report
7. As the admin, open the submitted expense report
8. Click on 'More' > 'Change workspace' > select a different WS

Expected Result:

The admin is able to change the expenses to another WS

Actual Result:

The admin is unable to change the workspace for the expenses; an error is thrown

Workaround:

Unknonw

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

Bug6851989_1749168241243.Screen_Recording_2025-06-05_at_8.44.49_PM.mp4

View all open jobs on GitHub

[melvin-bot]

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

[flaviadefaria]

cc @luacmartins for visibility -- should we assign this to someone working on the project?

[luacmartins]

@flaviadefaria I think this is a duplicate (or at least has the same root cause as https://github.com/Expensify/Expensify/issues/503415). We just merged the last PR to fix that issue, so we should retest once this PR hits prod

[melvin-bot]

@flaviadefaria Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@flaviadefaria Still overdue 6 days?! Let's take care of this!

[flaviadefaria]

The linked PR has been deployed this is ready to be re-tested.