Expense - Error when editing Attendee field when attendees are added from OD

[mitarachim]

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.40-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: #60067
Email or phone of affected tester (no customers): sdjmodjosijodis@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Create workspace in ND , if there's nor workspace.

1. Go to staging.expensify.com
2. Go to Reports.
3. Create a report and add an expense without adding new attendees.
4. Click on the expense, add some attendees and save it.
5. Log in to staging.new.expensify.com with the same account.
6. Go to workspace chat.
7. Go to transaction thread of the expense created from OD in Step 3.
8. Click Attendees.
9. Unselect any attendee which is added from OD.
10. Click Save.

Expected Result:

The new changes will be saved without error.

Actual Result:

App throws error when removing attendees that are added from OD, but the changes are still saved.

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

Bug6822684_1746502278070.20250506_112853.mp4

View all open jobs on GitHub

[melvin-bot]

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

[madmax330]

I'm not able to reproduce this on staging:

Screen.Recording.2025-05-06.at.4.50.21.PM.mov