Skip to content

[Due for payment 2025-08-15] [$250] Group - Group chat remains displayed on "Search" on member´s side after being removed. #67026

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.1.85-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2148171/test-runs/TR-183/folder/12015268/39317143/801695824
Email or phone of affected tester (no customers): ibellicotest+1403@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app)
App Component: Search

Action Performed:

Prerequisite: Have two accounts opened on two different devices or environments.

  1. Open the Expensify app.
  2. Tap on FAB and select "Star Chat"
  3. Add User B and other members to a group chat.
  4. Complete the creation flow.
  5. Once redirected to chat, send a message to it.
  6. As User B, open the just created group and return to Inbox.
  7. As User A, remove User B from group.
  8. As User B, note that group chat disappears from LHN.
  9. Tap on the search icon on the top left corner.
  10. Note that group chat is still displayed on search list, despite not being member anymore.
  11. Open the chat.
  12. Note that you are redirected to a "It´s not here" page.

Expected Result:

After being removed from a group chat, member shouldn´t be able to find the chat on "Search".

Actual Result:

Group chat is still displayed on "Search" on member´s side, after being removed from it. Opening the chat from search list, navigates to a "It´s not here" page.

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

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021948746667930568526
  • Upwork Job ID: 1948746667930568526
  • Last Price Increase: 2025-07-25
  • Automatic offers:
    • mkzie2 | Contributor | 108221772
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @alexpensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @alexpensify (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. melvin-bot commented on Jul 24, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jul 24, 2025

    @melvin-bot

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

  5. github-actions commented on Jul 24, 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.
  6. rushatgabhane commented on Jul 24, 2025

    @rushatgabhane
    Member

    @BlameGPT find offending pulls

  7. BlameGPT commented on Jul 24, 2025

    @BlameGPT
    Contributor

    Lowkey sus PRs fr fr

    If not above, check these

  8. iwiznia commented on Jul 24, 2025

    @iwiznia
    Contributor

    I don't think this merits being a blocker, as it's a link on recent chats and then we error when you try to access it.
    One could even argue is correct behavior (that was one of my recent chats, the fact that I can't access it anymore does not mean I should not see it there). What do you think @alexpensify?

  9. 25 remaining items

  10. mkzie2 commented on Jul 30, 2025

    @mkzie2
    Contributor

    @thesahindia The PR is ready.

  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Aug 8, 2025
  12. changed the title [-][$250] Group - Group chat remains displayed on "Search" on member´s side after being removed.[/-] [+][Due for payment 2025-08-15] [$250] Group - Group chat remains displayed on "Search" on member´s side after being removed.[/+] on Aug 8, 2025
  13. melvin-bot commented on Aug 8, 2025

    @melvin-bot

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

  14. melvin-bot commented on Aug 8, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.90-11 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 2025-08-15. 🎊

    For reference, here are some details about the assignees on this issue:

  15. melvin-bot commented on Aug 8, 2025

    @melvin-bot

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

  16. alexpensify commented on Aug 15, 2025

    @alexpensify
    Contributor

    Payment Summary

    Contributor: @mkzie2 paid $250 via Upwork
    Contributor+: @thesahindia due $250 via NewDot

  17. twisterdotcom commented on Sep 3, 2025

    @twisterdotcom
    Contributor

    @thesahindia has submitted payment for this report on ND here.

    SO: https://stackoverflowteams.com/c/expensify/questions/7582

    Zapier Logs Run ID: 00040eee-a054-a098-b618-ab00f9e2d7b1
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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions