Skip to content

[Due for payment] [$250] Chat - Infinite loading on member´s side, when removed from WS chat. #64627

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.69-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory
Email or phone of affected tester (no customers): ibellicotest+1122@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome (mWeb - Hybrid App) / Windows 10 - Chrome
App Component: Chat Report View

Action Performed:

Prerequisite: Have two accounts opened on two different devices or environments.
Prerequisite 2: User A has at least one workspace created.

  1. Open the Expensify app.
  2. As User A open any workspace chat.
  3. Tap on header and select "Members"
  4. Invite User B as member,
  5. Return to chat and create a manual expense.
  6. As User B open the workspace chat.
  7. Open the report of the just received expense.
  8. As User A, remove User B from workspace chat.
  9. As User B, tap on the back button on the top left corner to return to chat. (Device´s back button on Web)
  10. Note that a page with infinite loading is displayed.

Expected Result:

When member of a workspace is removed from chat while on expense report, navigating back should redirect to inbox.

Actual Result:

Infinite loading is displayed, when a member of a workspace navigates back from expense report to chat after being removed as member.

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/~021940110451634713328
  • Upwork Job ID: 1940110451634713328
  • Last Price Increase: 2025-07-01
  • Automatic offers:
    • situchan | Contributor | 109998549
Issue OwnerCurrent Issue Owner: @laurenreidexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 20, 2025
  2. melvin-bot commented on Jun 20, 2025

    @melvin-bot

    Triggered auto assignment to @Christinadobrzyn (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 Jun 23, 2025

    @melvin-bot

    @Christinadobrzyn Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  4. Christinadobrzyn commented on Jun 23, 2025

    @Christinadobrzyn
    Contributor

    not sure if we want to do this one... asking

  5. Christinadobrzyn commented on Jun 24, 2025

    @Christinadobrzyn
    Contributor

    Getting more info from QA about the affected platforms before asking the team - https://expensify.slack.com/archives/C9YU7BX5M/p1750795137912069

  6. IuliiaHerets commented on Jun 25, 2025

    @IuliiaHerets

    @Christinadobrzyn Issue still repro iOS 18.5 / App version 9.1.71-1

    Repro_64627.mp4
  7. nabi-ebrahimi commented on Jun 27, 2025

    @nabi-ebrahimi

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Chat - Infinite loading on member´s side, when removed from WS chat.

    What is the root cause of that problem?

    When User B is removed from the workspace members list, they lose access to the report specified by the reportID stored in the backTo param. Clicking the back button redirects User B to the backTo URL, which results in a "Not Found" error because they no longer have access to the report.

    What changes do you think we should make in order to solve the problem?

    To solve this, we can store the report ID in a ref. then in useFocusEffect, check if report?.reportID already exists in this page and does not exist now. So it means this user got removed from the workspace they already have access to. So, redirect back to the inbox.

    Update src/pages/home/ReportScreen.tsx

      const reportIdRef = useRef<string | undefined>(null);
    
        useFocusEffect(() => {
            if (!reportIdRef.current && reportOnyx?.reportID) {
                reportIdRef.current = reportOnyx?.reportID;
            } else {
                if (reportOnyx?.reportID) {
                    return;
                }
                Navigation.goBack();
            }
        });

    What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

    None

    What alternative solutions did you explore? (Optional)

    Screen.Recording.1404-04-06.at.2.36.16.PM.mov
  8. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    @Christinadobrzyn Eep! 4 days overdue now. Issues have feelings too...

  9. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    @Christinadobrzyn Eep! 4 days overdue now. Issues have feelings too...

  10. 141 remaining items

  11. added and removed on Apr 7, 2026
  12. amyevans commented on Apr 7, 2026

    @amyevans
    Contributor

    I believe Lauren is just getting back from OOO so appreciate your patience but I've reopened in the meantime!

  13. changed the title [-][Held on #80306] [BACK BUTTON] [$250] Chat - Infinite loading on member´s side, when removed from WS chat.[/-] [+][Due for payment] [$250] Chat - Infinite loading on member´s side, when removed from WS chat.[/+] on Apr 7, 2026
  14. laurenreidexpensify commented on Apr 8, 2026

    @laurenreidexpensify
    Contributor
  15. nabi-ebrahimi commented on Apr 8, 2026

    @nabi-ebrahimi

    @laurenreidexpensify , I've applied. thanks.

  16. melvin-bot commented on Apr 13, 2026

    @melvin-bot

    @laurenreidexpensify Eep! 4 days overdue now. Issues have feelings too...

  17. laurenreidexpensify commented on Apr 15, 2026

    @laurenreidexpensify
    Contributor

    @nabi-ebrahimi apologies I was offline for a few days - contract sent in Upwork

  18. laurenreidexpensify commented on Apr 15, 2026

    @laurenreidexpensify
    Contributor

    Payment Summary

    @nabi-ebrahimi paid $250 in Upwork

  19. JmillsExpensify commented on Apr 16, 2026

    @JmillsExpensify
    Contributor

    Payment summary above is accurate.

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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions