Reports-Report is not selected but still highlighted when creating a new report while selected

[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.46-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #70877
Email or phone of affected tester (no customers): jsnoidjdosisjdios@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 26.1
App Component: Search

Action Performed:

1. Launch Expensify app.
2. Go to Reports > Reports.
3. Tap + > Create report.
4. Tap app back button.
5. Long tap on the empty report > Select.
6. Tap + > Create report.
7. Tap app back button.

Expected Result:

The report in Step 5 will no longer be selected.

Actual Result:

The report in Step 5 is no longer be selected, but still 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

Bug6996695_1762489536233.ScreenRecording_11-07-2025_12-23-24_1.1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @Christinadobrzyn (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 @danieldoglas (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.