Room - Infinite loading when user is removed from room while in RHP #59126

thelullabyy · 2025-03-26T05:04:11Z

Explanation of Change

Fixed Issues

$#58235
PROPOSAL:#58235 (comment)

Tests

Open the App
Open any private room chat or create one if necessary.
Tap on room header and select "Members"
Invite another user to the room.
Switch to User B account.
Open the room and tap on the header.
While User B stays on RHP, switch to User A account again.
Tap on room header and select "Members"
Remove User B from room chat.
Switch to User B account again.
Note that a "It´s not here" screen is displayed.
Tap on the arrow on the top left corner.
Verify back to Report List page without infinite loading

Verify that no errors appear in the JS console

Offline tests

QA Steps

Open the App
Open any private room chat or create one if necessary.
Tap on room header and select "Members"
Invite another user to the room.
Switch to User B account.
Open the room and tap on the header.
While User B stays on RHP, switch to User A account again.
Tap on room header and select "Members"
Remove User B from room chat.
Switch to User B account again.
Note that a "It´s not here" screen is displayed.
Tap on the arrow on the top left corner.
Verify back to Report List page without infinite loading

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android_native.mp4

Android: mWeb Chrome

android_chorme.mp4

iOS: Native

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

chorme.mp4

MacOS: Desktop

desktop.mp4

melvin-bot · 2025-03-26T05:22:58Z

@allroundexperts Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

mountiny · 2025-03-26T23:17:18Z

@allroundexperts what is your eta? thanks!

allroundexperts · 2025-04-03T06:08:13Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

Screen.Recording.2025-04-03.at.12.20.04.PM.mov

iOS: Native

Screen.Recording.2025-04-03.at.12.19.08.PM.mov

iOS: mWeb Safari

Screen.Recording.2025-04-03.at.12.17.52.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2025-04-03.at.12.12.58.PM.mov

MacOS: Desktop

Screen.Recording.2025-04-03.at.12.15.32.PM.mov

allroundexperts · 2025-04-03T07:28:40Z

I am unable to test this on Android because pusher notification is not coming along.

Screen.Recording.2025-04-03.at.12.23.21.PM.mov

allroundexperts

Looks good. I posted the issue for Android, but that is becayse of pusher notifications not being received.

mountiny · 2025-04-03T17:08:53Z

src/pages/home/ReportScreen.tsx

+            const currentRoute = navigationRef.getCurrentRoute();
+            const isReportDetailOpenInRHP =
+                isTopMostReportId &&
+                [...Object.values(SCREENS.REPORT_DETAILS), ...Object.values(SCREENS.REPORT_SETTINGS), ...Object.values(SCREENS.PRIVATE_NOTES)].find((r) => r === currentRoute?.name) &&


Could you move this [...Object.values(SCREENS.REPORT_DETAILS), ...Object.values(SCREENS.REPORT_SETTINGS), ...Object.values(SCREENS.PRIVATE_NOTES)] out of scope of the method so its not computed every time? I think this can be done just once

@mountiny Good catch, i updated. Please help to check again.

mountiny · 2025-04-07T18:25:06Z

src/pages/home/ReportScreen.tsx

@@ -526,6 +526,7 @@ function ReportScreen({route, navigation}: ReportScreenProps) {
        // eslint-disable-next-line react-compiler/react-compiler, react-hooks/exhaustive-deps
    }, [prevIsFocused, report?.participants, isFocused, isSingleTransactionView, reportID]);

+    const reportDetailScreens = [...Object.values(SCREENS.REPORT_DETAILS), ...Object.values(SCREENS.REPORT_SETTINGS), ...Object.values(SCREENS.PRIVATE_NOTES)];


Could this be moved even out of the ReportScreen function? cc @allroundexperts

The Screens wont really ever change in the render cycle so we could move it out of the component completely

@mountiny I updated

mountiny

Thanks!

OSBotify · 2025-04-08T11:30:00Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2025-04-09T04:40:18Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.1.25-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

github-actions · 2025-04-10T00:56:07Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.1.25-4 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	failure ❌
🍎 iOS 🍎	success ✅

fix: infinite loading when user is removed from room

0d42da9

thelullabyy marked this pull request as ready for review March 26, 2025 05:22

thelullabyy requested a review from a team as a code owner March 26, 2025 05:22

melvin-bot bot requested review from allroundexperts and removed request for a team March 26, 2025 05:22

mountiny assigned thelullabyy Mar 26, 2025

allroundexperts approved these changes Apr 3, 2025

View reviewed changes

melvin-bot bot requested a review from mountiny April 3, 2025 07:34

mountiny reviewed Apr 3, 2025

View reviewed changes

refactor code

4a428d9

mountiny reviewed Apr 7, 2025

View reviewed changes

refactor: move const report detail screens out of function

5af4bb5

mountiny approved these changes Apr 8, 2025

View reviewed changes

mountiny merged commit 0beba9b into Expensify:main Apr 8, 2025
17 checks passed

github-actions bot mentioned this pull request Apr 9, 2025

Deploy Checklist: New Expensify 2025-04-09 #59866

Closed

66 tasks

melvin-bot bot mentioned this pull request Apr 10, 2025

[Due for payment 2025-04-17] [$250] Room - Infinite loading when user is removed from room while in RHP #58235

Closed

8 tasks

ishakakkad mentioned this pull request May 5, 2025

[$250] Reports-RHP loads infinitely after deleting expense in report that has deleted expense with reply #60624

Open

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Room - Infinite loading when user is removed from room while in RHP #59126

Room - Infinite loading when user is removed from room while in RHP #59126

Uh oh!

thelullabyy commented Mar 26, 2025

Uh oh!

melvin-bot bot commented Mar 26, 2025

Uh oh!

mountiny commented Mar 26, 2025

Uh oh!

allroundexperts commented Apr 3, 2025 •

edited

Loading

Uh oh!

allroundexperts commented Apr 3, 2025

Uh oh!

allroundexperts left a comment

Uh oh!

mountiny Apr 3, 2025

Uh oh!

thelullabyy Apr 5, 2025

Uh oh!

mountiny Apr 7, 2025

Uh oh!

mountiny Apr 7, 2025

Uh oh!

thelullabyy Apr 8, 2025

Uh oh!

mountiny left a comment

Uh oh!

Uh oh!

OSBotify commented Apr 8, 2025

Uh oh!

github-actions bot commented Apr 9, 2025

Uh oh!

github-actions bot commented Apr 10, 2025

Uh oh!

Uh oh!

Room - Infinite loading when user is removed from room while in RHP #59126

Room - Infinite loading when user is removed from room while in RHP #59126

Uh oh!

Conversation

thelullabyy commented Mar 26, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 26, 2025

Uh oh!

mountiny commented Mar 26, 2025

Uh oh!

allroundexperts commented Apr 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

allroundexperts commented Apr 3, 2025

Uh oh!

allroundexperts left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny Apr 3, 2025

Choose a reason for hiding this comment

Uh oh!

thelullabyy Apr 5, 2025

Choose a reason for hiding this comment

Uh oh!

mountiny Apr 7, 2025

Choose a reason for hiding this comment

Uh oh!

mountiny Apr 7, 2025

Choose a reason for hiding this comment

Uh oh!

thelullabyy Apr 8, 2025

Choose a reason for hiding this comment

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Apr 8, 2025

Uh oh!

github-actions bot commented Apr 9, 2025

Uh oh!

github-actions bot commented Apr 10, 2025

Uh oh!

Uh oh!

allroundexperts commented Apr 3, 2025 •

edited

Loading