-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android - Chat - App crashes after creating different chats back to back #51131
Comments
👋 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 ( |
Triggered auto assignment to @JmillsExpensify ( |
💬 A slack conversation has been started in #expensify-open-source |
We think that this bug might be related to #wave-collect - Release 1 |
This is not related to #wave-collect but the app crashing is worrying, so we should look into this one. |
So far I can't reproduce on the standalone app, going to test with HybridApp. |
Ok with HybridApp I managed to repro with the given steps, and now I get a crash immediately when I open the app, even on a fresh sign-in. |
Still trying to build HybridApp in dev, it's extremely slow and I keep running into different errors... In the meantime I found you can reproduce by just opening and closing the new chat menu multiple times in a row, no need to actually create chats. |
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
Bug6639737_1729351117916.Crash.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: