Group - Website crashes when leaving group chat.

[mitarachim]

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.0.80-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5395271&group_by=cases:section_id&group_order=asc&group_id=229067
Email or phone of affected tester (no customers): Ibellicotest+133@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola Moto G60/ Android 12 - Windows 10/ Chrome
App Component: Other

Action Performed:

1. Open the staging.new.expensify.com website.
2. Open any group chat or create one if necessary.
3. Tap on group header.
4. Tap on "Leave"

Expected Result:

The user should land on LHN after leaving a group chat and this group should be automatically deleted.

Actual Result:

Website crashes when the user tries to leave a group chat.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6704688_1735688754617!log.txt

Bug6704688_1735685266778.036ae052-9dd9-4ba8-b5ea-902264a81ccc.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

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

[NJ-2020]

Offending PR: #53902

We remove the default ID CONST.DEFAULT_NUMBER_ID here, but since these value can undefined so it will throw an error

App/src/pages/home/HeaderView.tsx

Line 77 in e5108a1

const [parentReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${report?.parentReportID || report?.reportID}`);

---

We can add the default ID in case if this value is undefined

const [parentReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${report?.parentReportID || report?.reportID || CONST.DEFAULT_NUMBER_ID}`);