[Due for payment 2026-01-27] Room - Details page remain open when owner leave custom room

[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.3.3-2
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-2989/folder/13176685/41236597/1128448384?sort=-status_id
Email or phone of affected tester (no customers): gocemate+b215490617@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 10/Chrome
App Component: Other

Action Performed:

1. Create custom room
2. Go to header
3. Click Leave option

Expected Result:

RHP details modal should close

Actual Result:

Details page remains open when owner leave room

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @heyjennahay

[melvin-bot]

Triggered auto assignment to @heyjennahay (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.

[github-actions]

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

[melvin-bot]

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

[melvin-bot]

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

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: No single recent PR caused this - appears to be a long-standing inconsistency
Root Cause Location: /src/libs/actions/Report.ts

Recommendation: ROLL FORWARD

The leaveRoom function needs to be updated to include navigation logic, similar to leaveGroupChat.

Labels: No label changes needed - this is correctly labeled as DeployBlockerCash (App deploy blocker).

Detailed Analysis

Evidence

The issue occurs when an owner leaves a custom room. The flow is:

1. User clicks "Leave" in ReportDetailsPage
2. leaveChat() callback calls leaveRoom(report.reportID, currentUserAccountID, isWorkspaceMemberLeavingWorkspaceRoom)
3. leaveRoom updates Onyx state but does NOT trigger any navigation
4. RHP (ReportDetailsPage) remains open

Root Cause

In /src/libs/actions/Report.ts:

leaveGroupChat (line 3754):

navigateToMostRecentReport(report);
API.write(WRITE_COMMANDS.LEAVE_GROUP_CHAT, {reportID}, {optimisticData, successData, failureData});

leaveRoom (line 3858):

API.write(WRITE_COMMANDS.LEAVE_ROOM, parameters, {optimisticData, successData, failureData});
// No navigation logic!

The inconsistency: leaveGroupChat calls navigateToMostRecentReport(report) to close the RHP and navigate away, but leaveRoom does not.

Verification

Checked:

• /src/libs/actions/Report.ts - Confirmed leaveRoom lacks navigation
• /src/pages/ReportDetailsPage.tsx lines 332-341 - Confirmed leaveChat callback calls leaveRoom without handling navigation afterwards
• navigateToMostRecentReport function (line 3658) - Handles proper RHP dismissal via Navigation.goBack()

Fix Needed

The leaveRoom function should call navigateToMostRecentReport(report) before the API call, similar to leaveGroupChat. However, care must be taken to handle the isWorkspaceMemberLeavingWorkspaceRoom case where the user should NOT be navigated away (they remain in the room with hidden notification preference).

[lakchote]

Coming from #77657 (tested the revert on dev - it solves the issue) @collectioneur @WojtekBoman @mountiny @ZhenjaHorbach

I don't think this should be a blocker though, it's an UI bug on a non-critical flow