-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-12-19] Fix the pusher instance not found crash #53752
Comments
Triggered auto assignment to @mallenexpensify ( |
Hello, I'm from SoftwareMansion and I'll work on this issue |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.74-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-19. 🎊 For reference, here are some details about the assignees on this issue:
|
@allroundexperts @mallenexpensify @allroundexperts The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Hey, I think the PR fixing this caused #54142. Please take a look 👀 |
$125 for @allroundexperts as there was a regression from this PR |
Payment Summary
BugZero Checklist (@mallenexpensify)
|
Contributor+: @allroundexperts due $125 via NewDot Do we want a test case for this? Or one updated? |
@mallenexpensify, @allroundexperts, @mountiny, @jnowakow Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I don't think we need a test case for this. In the PR, the test steps just mentioned opening the app and verifying if it crashed or not. |
We are seeing this specific crash error in firebase that we have not been able to easily reproduce but we can see that its happening:
Here is a link to firebase for the crash
Issue Owner
Current Issue Owner: @mallenexpensifyThe text was updated successfully, but these errors were encountered: