You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-01-07] Search - Triggering a search within a conversation for first time leads to "Approve" section #76503
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:
Open the Expensify app.
Sign up with a new account.
Complete onboarding modal selecting "Track and budget expenses"
Once you land on "Inbox", create first workspace.
Open any individual chat. (For example: Self DM)
Send a message to chat.
Tap on the search icon on the top right corner.
Tap on the option to trigger a search within the conversation.
Type the just sent message and trigger a search.
Note that you land on "Approve" section instead of landing on the search results.
Use device´s back button.
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.
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Search - Triggering a search within a conversation for first time leads to "Approve" section[/-][+][Due for payment 2026-01-07] Search - Triggering a search within a conversation for first time leads to "Approve" section[/+]on Dec 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.89-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@ShridharGoel / @Krishna2323 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Dec 2, 2025
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 commentedon Dec 2, 2025
👋 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:
melvin-bot commentedon Dec 2, 2025
Triggered auto assignment to @JS00001 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 2, 2025
💬 A slack conversation has been started in #expensify-open-source
JS00001 commentedon Dec 2, 2025
@ShridharGoel @Krishna2323 Could you take a look?
27 remaining items
[-]Search - Triggering a search within a conversation for first time leads to "Approve" section[/-][+][Due for payment 2026-01-07] Search - Triggering a search within a conversation for first time leads to "Approve" section[/+]melvin-bot commentedon Dec 31, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.89-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-01-07. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Dec 31, 2025
@ShridharGoel / @Krishna2323 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Krishna2323 commentedon Jan 7, 2026
@jasperhuangg this can be closed now, the fix is on the prod.