[RCA #72034] Search - type:expense-report action:approve to:me appears repeatedly

[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.2.61-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #72034
Email or phone of affected tester (no customers): sjodnjodjosjnois@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

1. Go to staging.new.expensify.com
2. Log in with new account.
3. Create a workspace.
4. Go to Reports tab.
5. Wait for Approve tab to load.
6. Go to Inbox.
7. Wait for app to load first.
8. Tap search icon on the top right.
9. Wait for a while.
10. Type any email.
11. Clear the search field.
12. Type any email.
13. Clear the search field.

Expected Result:

type:expense-report action:approve to:me will only appear once.

Actual Result:

type:expense-report action:approve to:me appears repeatedly.

Multiple "type:expense-report action:approve to:me" are highlighted together.

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

Bug7009060_1763631031869.Screen_Recording_20251120_172949_Chrome.mp4

View all open jobs on GitHub

[melvin-bot]

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