Open IuliiaHerets opened 3 hours ago
: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:
Triggered auto assignment to @francoisl (DeployBlockerCash
), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.
Triggered auto assignment to @JmillsExpensify (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
We think that this bug might be related to #wave-collect - Release 1
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.51-1 Reproducible in staging?: Y Reproducible in production?: N If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The app should continue to work smoothly while the user creates new chats back to back.
Actual Result:
The app crashes after the user creates a few chats back to back.
Workaround:
Unknown
Platforms:
Screenshots/Videos
1910_2.txt
https://github.com/user-attachments/assets/b9b3a8a6-1c3d-4f6b-aad3-643ac767dd28
View all open jobs on GitHub