-
Notifications
You must be signed in to change notification settings - Fork 617
firebase/firestore: rejected task using com.google.firebase.firestore.util.AsyncQueue #405
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
Comments
Thank you for reporting the issue. The exception seems to be coming from deep inside gRPC internals. Can you provide any additional information? Are there any specific steps that trigger the exception? Would it be possible for you to obtain a log? ( |
Not sure that crashlytics is going to report the output of logcat if setLoggingEnabled is set to true. It would be nice if you can give me some notes/direction on how to deploy the application with these settings. This is the complete stack trace of the crash with information regarding all threads: |
Thank you for the full stack trace. Unfortunately, at the moment Firestore logs cannot be extracted from Crashlytics. If this issue is critical for you, we could give you guidance on how to achieve that -- it would require code changes to Firestore. The exception that triggered the crash is actually secondary. It is raised when Firestore async queue is shut down, but something (gRPC in this case) still tries to enqueue a task on it. The root cause is whatever made the async queue shut down -- unfortunately, it is not represented in the stack trace. We plan to add some defensive code to the async queue to make sure the original exception doesn't vanish without a trace. One more question -- do you see any other crashes in Crashlytics that could plausibly be the same issue? Because the root issue is that async queue got shut down, it may manifest with a different stack trace. |
Here is another one that might be related.
The strange thing here is that device memory usage is really low and I'm not sure that memory is the real cause of the problem: The complete stack trace: |
Got another similar exception:
|
This last stack trace doesn't really tell us anything. After's there's been a failure of some kind, Firestore shuts down its internal queue. What's happening here is that something is trying to execute an on-completion handler on that queue after a crash but failing to do so. There's no indication what was trying to run though. In any case this is already a secondary failure. Something else is the actual failure and isn't indicated here. |
Hi Everyone, case 1:- "main" prio=5 tid=1 Waiting waiting on <0x13be0a86> (a java.lang.Object) case 2:- //firebase lib // sdk version for more details regard to this ANR please look |
@Pratyesh your stack traces are related to Firebase Messaging, but this issue is related to Firestore. Please create a new issue with as many details as you can share so that the Messaging team can help. |
Happened when running inside of JUnit, and also having the work submitted to an ExecutorService.
|
E/AndroidRuntime: FATAL EXCEPTION: main my application crashes when trying to run the application and shows the following error!! |
@sag-007 though the exception name is in common with the one in this issue, you’re using the Realtime Database, not Firestore. Please open a new issue with all the details in the template. |
Fatal Exception: java.util.concurrent.RejectedExecutionException |
Hi @mgenov, just bumping this thread. May I ask if you're still encountering this issue on the latest SDK? |
Hey @mgenov. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Since there haven't been any recent updates here, I am going to close this issue. @mgenov if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this. |
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Got this stack trace from crashlytics:
Here is the device information:

Steps to reproduce:
It happens rarely but the amount of devices in production is less than 100.
Relevant Code:
N/A
The text was updated successfully, but these errors were encountered: