Open IuliiaHerets opened 1 day ago
Triggered auto assignment to @madmax330 (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
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.
💬 A slack conversation has been started in #expensify-open-source
:wave: 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:
@madmax330 The same RCA with https://github.com/Expensify/App/issues/52864.
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.65-0 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5247671&group_by=cases:section_id&group_order=asc&group_id=229067 Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
User should be able to leave and the group should disappear from LHN.
Actual Result:
Website crashes after leaving a group chat. Error Message - "Uh oh, something went wrong." Issue occasionally reproduces on Web and reproduces every time on mWeb.
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/7772911a-6793-46e2-9ab6-470326aaf724
2111_2.txt
View all open jobs on GitHub