Repository navigation
Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: v9.4.45-4
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #96734
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Windows 11 / Chrome, iPhone 13 / iOS 27 Beta, Samsung Galaxy A52 / Android 14
App Component: Workspace Settings
Action Performed:
Preconditions:
-prepare 2 accounts (user A & user B)
- user A create 2 workspace (Alfa & Beta) and invite user B to both workspaces
Steps:
- as User A create room in Alfa and Invite User B to that room member
- as User B go to Alfa -> #rooms and validate that new room exists
- as User A invite another user to the room
- as User B check that members count is updated, then navigate to room chat
- as User A remove user B from the room
- as User B note that it automatically navigated to concierge room
- as user B navigate to Alfa -> #room
Expected Result:
the room shouldn't visible to user B's side and user B can't access to the room chat since user A already removed user B from room member. this also should be in accordance with automatically navigated to concierge chat in step 7
Actual Result:
Room is still visible on user B's side after user A removing it from room member
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7220066_1785256852557.bandicam_2026-07-28_23-25-32-537.mp4
Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7220066
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~022082150919023007913
- Upwork Job ID: 2082150919023007913
- Last Price Increase: 2026-07-28
Issue Owner
Current Issue Owner: @marcaaronMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
applause-bot commentedon Jul 28, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/7f253c04aacb7d5757f5f1d4da6ccc6eb6b00f1a2bcf38b35d4d3e3533138541
MelvinBot commentedon Jul 28, 2026
Issue Analysis
Root Cause: A room's visibility in User B's LHN and their ability to open it are computed purely from local Onyx report state — the report existing,
notificationPreference !== 'hidden', andcanAccessReport(which only checks the default-room beta +errorFields.notFound). There is no membership/participant gate anywhere in this pipeline, and chat rooms are explicitly allowed to show even with no participants. So being removed from a room does not, by itself, hide it.When User A removes User B, the
removeFromRoomaction only writes the participant removal to User A's Onyx (Report/index.ts:5277-5342). Nothing sets User B's ownnotificationPreferencetohidden— unlike voluntarily leaving a room, which does (Report/index.ts:4954-4972). That's why leaving hides the room but being removed does not.The auto-navigation to Concierge (step 7) fires only because the backend transiently clears the report from User B's Onyx, which trips
wasReportRemovedinReportNavigateAwayHandler.tsx:148-198. But that clearing isn't durable: when User B navigates back to Workspace → #rooms and opens the room,withReportOrNotFound/ the LHN callsOpenReport(Report/index.ts:1534), the room is re-served and re-populated in Onyx (itssuccessDataeven clearserrorFields.notFound), and with nohiddenpreference and nonotFoundflag the room reappears and reopens.Where the fix lives: The durable state the App relies on to hide/block a room (a
hiddennotification preference for the removed user,errorFields.notFound, an archive flag, or simply not re-serving the room to a non-member onOpenReport) has to be pushed by the backend on member removal — the way voluntary leave already results in a hidden preference. This appears to be a backend/internal issue and a separate internal investigation is needed. It should be escalated to an internal engineer; a frontend-only change in App can't reliably fix it because App has no authoritative membership signal to gate on once the backend keeps serving the room.Investigation details & evidence
reasonForReportToBeInOptionList/shouldReportBeInOptionList,ReportUtils.ts:9841-10033— rooms bypass the "no participants" exclusion; nothing checksisReportParticipant(currentUser).SidebarUtils.ts:326-378only checksisHiddenForCurrentUser+shouldReportBeInOptionList.isHiddenForCurrentUser,ReportUtils.ts:2386-2397.withReportOrNotFound.tsx:104-140+canAccessReport,ReportUtils.ts:9366-9377— only default-room beta +errorFields.notFound, no membership check.Alternative explanation considered: that the App simply isn't reacting to a removal push. Ruled out — the auto-navigation in step 7 proves the removal update does reach User B; it's just transient (report cleared) rather than a durable hide, so re-opening re-fetches the room.
Open question (backend): exactly what Onyx update the backend pushes to the removed user on removal, and whether
OpenReportshould stop serving the room to a non-member — this determines the precise backend fix and can't be confirmed from the App repo alone.Confidence: Medium — the App-side behavior (no membership gate; removal never sets a durable hide locally) is verified in code, but the exact fix requires backend behavior that isn't visible from this repo.
Next Steps: Reply with
@MelvinBot <your feedback>to refine this analysis.melvin-bot commentedon Jul 28, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @brunovjk (
External)melvin-bot commentedon Jul 28, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022082150919023007913
brunovjk commentedon Jul 31, 2026
I agree with MelvinBot’s analysis here. This looks like it needs an internal/backend fix rather than an App-only fix. Could you please help confirm whether this should be handled purely on the backend? Thank you.
🎀 👀 🎀 C+ reviewed
melvin-bot commentedon Jul 31, 2026
Triggered auto assignment to @marcaaron, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
melvin-bot commentedon Aug 3, 2026
@marcaaron Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Aug 5, 2026
@marcaaron Eep! 4 days overdue now. Issues have feelings too...
21 remaining items
melvin-bot commentedon Aug 28, 2026
@marcaaron 10 days overdue. Is anyone even seeing these? Hello?
brunovjk commentedon Sep 1, 2026
Not overdue
melvin-bot commentedon Sep 2, 2026
This issue has not been updated in over 14 days. @marcaaron, @brunovjk eroding to Weekly issue.
marcaaron commentedon Sep 17, 2026
This has been fixed in the backend now. Can we re-test?
marcaaron commentedon Oct 1, 2026
This is resolved now. Closing.