You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-12-19] Fix the pusher instance not found crash #53752
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:
Fatal Exception: com.facebook.react.common.JavascriptException: Error: TaskQueue: Error with task : [Pusher] instance not found. Pusher.subscribe()
most likely has been called before Pusher.init(), js engine: hermes, stack:
anonymous@1:3767030
processNext@1:847707
_processUpdate@1:846412
anonymous@1:524811
_callTimer@1:523728
_callReactNativeMicrotasksPass@1:523929
callReactNativeMicrotasks@1:525881
__callReactNativeMicrotasks@1:218344
anonymous@1:216543
__guard@1:218218
flushedQueue@1:216454
callFunctionReturnFlushedQueue@1:216310
at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:65)
at com.facebook.jni.NativeRunnable.run(NativeRunnable.java)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
at android.os.Looper.loopOnce(Looper.java:230)
at android.os.Looper.loop(Looper.java:319)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:235)
at java.lang.Thread.run(Thread.java:1012)
changed the title [-]Fix the pusher instance not found crash[/-][+][HOLD for payment 2024-12-19] Fix the pusher instance not found crash[/+]on Dec 12, 2024
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:
Activity
melvin-bot commentedon Dec 9, 2024
Triggered auto assignment to @mallenexpensify (
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.jnowakow commentedon Dec 9, 2024
Hello, I'm from SoftwareMansion and I'll work on this issue
[-]Fix the pusher instance not found crash[/-][+][HOLD for payment 2024-12-19] Fix the pusher instance not found crash[/+]melvin-bot commentedon Dec 12, 2024
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:
4 remaining items
melvin-bot commentedon Dec 19, 2024
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Dec 21, 2024
Contributor+: @allroundexperts due $125 via NewDot
Do we want a test case for this? Or one updated?
melvin-bot commentedon Dec 25, 2024
@mallenexpensify, @allroundexperts, @mountiny, @jnowakow Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
allroundexperts commentedon Dec 25, 2024
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.
melvin-bot commentedon Dec 27, 2024
@mallenexpensify, @allroundexperts, @mountiny, @jnowakow Huh... This is 4 days overdue. Who can take care of this?
mountiny commentedon Dec 28, 2024
I agree, I am not sure what would be a reliable test case for this one. We will monitor the crashes in firebase
mallenexpensify commentedon Dec 30, 2024
Thanks @allroundexperts and @mountiny, closing
JmillsExpensify commentedon Jun 10, 2025
$125 approved for @allroundexperts