[Due for payment 2026-01-07] Search - Triggering a search within a conversation for first time leads to "Approve" section

[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: 9.2.67-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: #75704
Email or phone of affected tester (no customers): ibellicotest+2134@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Search

Action Performed:

1. Open the Expensify app.
2. Sign up with a new account.
3. Complete onboarding modal selecting "Track and budget expenses"
4. Once you land on "Inbox", create first workspace.
5. Open any individual chat. (For example: Self DM)
6. Send a message to chat.
7. Tap on the search icon on the top right corner.
8. Tap on the option to trigger a search within the conversation.
9. Type the just sent message and trigger a search.
10. Note that you land on "Approve" section instead of landing on the search results.
11. Use device´s back button.
12. Note that now, you land on search results.

Expected Result:

After triggering a search within a conversation, user should automatically land on the search resutls.

Actual Result:

After triggering a search within a conversation for the first time, user lands on "Approve" section instead of landing on search results.
After landing on "Approve", using device´s back button, leads to search results.

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 @muttmuure (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.

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

Triggered auto assignment to @JS00001 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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

[JS00001]

@ShridharGoel @Krishna2323 Could you take a look?