Expense - Same attendee name appears twice in the list and can be selected twice

[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): applausetester+300402kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Click + > Create expense > Manual
4. Enter amount > Next.
5. On confirmation page, click Show more.
6. Click Attendees.
7. Enter a name (applee) and select the user.
8. Enter the same name again (applee).
9. Note that the same name appears twice. Do not select the same user.
10. Click Save.
11. Click Create expense.
12. Go to transaction thread.
13. Click Attendees.
14. Enter the same name from Step 7 (applee).
15. Select the duplicate name.
16. Click Save.
17. Note that the same name can be selected twice.

Expected Result:

In Step 9, the same name will not appear twice in the list.
In Step 17, the same name can only be selected once.

Actual Result:

In Step 9, the same name appears twice in the list.
In Step 17, the same name can be selected twice.

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

Bug6822628_1746495522141.20250506_093736.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @dylanexpensify (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 @robertjchen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source