Skip to content

Thread - Not here page when member leave room's thread #77140

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: v9.2.74-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: https://test-management.browserstack.com/projects/2219752/test-runs/TR-2322/folder/13176685/41236608/1065363062
Email or phone of affected tester (no customers): gocemate+b2155780@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Lenovo 80ES / Windows 10 Pro
App Component: Chat Report View

Action Performed:

  1. User A creates a room and invite User B
  2. User B reply on any message from the room and navigate back to room
  3. User A removes User B from the room
  4. User B open the thread page and Leave the thread

Expected Result:

Not here page should not open

Actual Result:

Not here page when member leave room's thread

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

    @melvin-bot

    Triggered auto assignment to @RachCHopkins (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 Dec 9, 2025

    @melvin-bot

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

  4. melvin-bot commented on Dec 9, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 9, 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. Nodebrute commented on Dec 9, 2025

    @Nodebrute
    Contributor

    Probably also caused by #76659

  7. brunovjk commented on Dec 9, 2025

    @brunovjk
    Contributor

    @lorretheboy can we fix this regression? Thank you.

  8. inimaga commented on Dec 9, 2025

    @inimaga
    Contributor

    We'll probably look to revert the PR given that its linked to multiple regressions as a well tested fix could take longer.

  9. brunovjk commented on Dec 9, 2025

    @brunovjk
    Contributor

    Thanks for handling it @inimaga

  10. inimaga commented on Dec 9, 2025

    @inimaga
    Contributor

    Requested a re-test from QA here.

  11. IuliiaHerets commented on Dec 9, 2025

    @IuliiaHerets

    @inimaga Not repro anymore for QA team, MacOS Monterey / Chrome, Web v9.2.74-2

    Screen.Recording.2025-12-09.at.22.32.08.mp4
  12. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Dec 9, 2025
  13. inimaga commented on Dec 9, 2025

    @inimaga
    Contributor

    Blocker resolved. Closing.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions