Report - The first item is highlighted when searching and selecting an expense

[jponikarchuk]

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: v9.2.65-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #75891
Email or phone of affected tester (no customers): htad26+ywtyregd@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10/Chrome, iPhone 13/iOS 26.1
App Component: Money Requests

Action Performed:

Precondition:
Have at least 15 unreported expenses

1. Navigate to staging.new.expensify.com
2. Create a new workspace > Create a report in the workspace chat
3. Create some expenses in the report
4. Navigate to Reports > Reports
5. Choose the unapproved report
6. Press More button > Add expense > Add unreported expense
7. In the text input search for an expense and select it
8. Scroll the page to the top of the list
9. Observe the first expense in the list

Expected Result:

The first expense should not be highlighted

Actual Result:

The first expense is highlighted

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

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @trjExpensify (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 @youssef-lr (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.

[youssef-lr]

Looking for the offending PR

[OlGierd03]

Looking for the offending PR

I'm not sure, but unfortunately I expect the PR with migrating the SelectionList to be a culprit