Skip to content

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

Closed

Description

@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

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 2, 2025
  2. melvin-bot commented on Dec 2, 2025

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

  3. github-actions commented on Dec 2, 2025

    @github-actions
    Contributor

    👋 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.
  4. melvin-bot commented on Dec 2, 2025

    @melvin-bot

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

  5. melvin-bot commented on Dec 2, 2025

    @melvin-bot

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

  6. JS00001 commented on Dec 2, 2025

    @JS00001
    Contributor

    @ShridharGoel @Krishna2323 Could you take a look?

  7. 27 remaining items

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 31, 2025
  9. 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
  10. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    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:

  12. melvin-bot commented on Dec 31, 2025

    @melvin-bot

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

  13. Krishna2323 commented on Jan 7, 2026

    @Krishna2323
    Contributor

    @jasperhuangg this can be closed now, the fix is on the prod.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions