-
Notifications
You must be signed in to change notification settings - Fork 585
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
Internal error in Cloud Firestore (25.1.0) #6365
Comments
Please address this issue ASAP because it's affecting my google play rankings. Thanks |
@alimurtaza28, we don't have enough information to move forward. It would be useful to know how your app is calling the Firestore API when this occurs. Also, capturing and providing us with debug logs from the SDK could help us investigate the issue further. Have you seen this issue with older versions of the SDK? Did it start occurring after you updated to a specific version of the SDK? |
Hey @alimurtaza28. 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! |
I'm having the same issue but it only happens one one of my devices, a Samsung Tab A. Here's the compete dump: java.lang.RuntimeException: Internal error in Cloud Firestore (25.1.0). Runs without a problem on my Oppo phone. I'm developing on a Dell XPF 13 running Linux, not that should matter. |
I have the same issue with Flutter - it only happens on first boot when interacting with Firestore, after restarting the app the issue is no longer present |
Also fails the same way when running on an emulated Samsung Tab A. |
Also the problem only occurs in my case during Google signin. After the user has signed in, the app runs without a problem. |
As per the comment by @MarkDuckworth above, please provide full debug logs to assist with debugging. Since we cannot reproduce we will need extra help with debugging and likely some back and forth. |
The same error happens to me too. It started happening to us when we updated the Flutter version to 3.24.3 and updated the Firebase libraries firebase_core 3.6.0 I really don't know what could cause the error since it happens to me randomly. In my particular case it happens to me on a Redmi 11 with Android 13 10-24 09:55:42.553 30930 30930 E Zygote : process_name_ptr:30930 com.xiaomi.mtb |
I'm also facing what seems to be the same error after Flutterflow's update to flutter 3.24.2. The app crashes immediately after startup: Fatal Exception: java.lang.RuntimeException: Internal error in Cloud Firestore (25.1.0). |
Same error |
Same issue here. It doesn't happen all the time, it happens randomly in different sessions and it is becoming such a big issue that we are considering downgrading the Flutter version (it seems to have something to do with both the combination of the Firebase version and the Flutter version) |
Is there any update on this case, it keeps happening to me randomly, I have tried several things mentioned here, however, nothing has worked for me
|
I am experiencing the same issue intermittently across different sessions, and it's starting to significantly impact our app's functionality. The bug appears to be random, but it's persistent. Im running latest flutter versión. |
Same error since the last update of FlutterFlow |
I'm trying to isolate this issue and get the right people involved. If you are replying to this thread to report the issue, please include the following information. If you've already replied and can also provide this info, please leave another comment.
These stack traces and logs are helpful. Thanks. |
One more question to help identify the issue: |
I'm going to limit this thread to |
I was able to find a possible cause of the Many reports of the error in this thread correlate with an update to Flutter. There may be a change in Flutter or any Flutter libraries you are using that are causing your app to create many If there are users that need a large number of |
Hey @alimurtaza28. 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! |
I am facing same issue in flutter 3.24.3
|
In my case, app only crash when it is logged in btw which uses firebase auth. without logged-in it is working fine. |
Hey @alimurtaza28. 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! |
Issue Details:
...
|
I'm having the same error but when trying to run test with detox 20.28.0 on mi emulator with the last version on Android Studio in RN 0.73.8. The app has crashed, see the details below:
|
It would be nicer if you could provide detailed information in this formate #6365 (comment) |
|
Hey @alimurtaza28. 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! |
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
App crashing in production mode with the following error:
Internal error in Cloud Firestore (25.1.0)
Caused by java.lang.RuntimeException: android.net.ConnectivityManager$TooManyRequestsException
Steps to reproduce:
It occurs randomly. I have seen this once on these devices : Samsung A32, Oppo A37, Samsung S8
What happened? How can we make the problem occur?
Fatal Exception: java.lang.RuntimeException: Internal error in Cloud Firestore (25.1.0).
at com.google.firebase.firestore.util.AsyncQueue.lambda$panic$3(AsyncQueue.java:546)
at com.google.firebase.firestore.util.AsyncQueue$$ExternalSyntheticLambda3.run(D8$$SyntheticClass)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7941)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:569)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)
Caused by java.lang.RuntimeException: android.net.ConnectivityManager$TooManyRequestsException
at com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor.lambda$executeAndReportResult$1(AsyncQueue.java:333)
at com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor$$ExternalSyntheticLambda2.run(D8$$SyntheticClass)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:487)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at com.google.firebase.firestore.util.AsyncQueue$SynchronizedShutdownAwareExecutor$DelayedStartFactory.run(AsyncQueue.java:235)
at java.lang.Thread.run(Thread.java:1012)
Relevant Code:
I don't yet know which code is causing this problem
// TODO(you): code here to reproduce the problem
The text was updated successfully, but these errors were encountered: