[Due for payment 2025-04-23] Search - Own account appears twice in search result after tracking expense in self DM

[nlemma]

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.18-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: #55460
Email or phone of affected tester (no customers): testtesttesttesttesttesttesttesttesttesttesttest8888+test@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Search

Action Performed:

Precondition:

• Account has self DM.
• Account is new (so that it is easy to see search results).

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Track a manual expense.
4. Open search router.
5. Type from:

Expected Result:

Own account will appear once in the search result.

Actual Result:

Own account appears twice in the search result - One is email, the other one is display name.
The same issue also happens with to: query.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6780963_1742854502458.20250325_053044.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @MonilBhavsar

[melvin-bot]

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

[nlemma]

@isabelastisser FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[MonilBhavsar]

Commented on the offending PR #55460

[MonilBhavsar]

Meanwhile, I am looking into fix