-
Notifications
You must be signed in to change notification settings - Fork 612
Internal error caused by java.util.NoSuchElementException #999
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
I found a few problems with this issue:
|
Hi @dimipaun Thanks for filing this issue. The error logs is similar to issue#890. To check whether if this is a implementation issue, could you try to remove all third-party APIs and follow this Quickstart guide and see if you'll still encounter the issue? |
Hey @dimipaun. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 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! |
Hi @aguatno , I don't think this is similar to #890 -- there the default Firebase App was deleted and a new one was created, thus causing the issue. No such thing in this case -- we just use the default app. Plus, this issue happens sporadically in production only, so there's no way to "remove all third-party libraries" as that would mean there would be no app left to deploy! What I did notice is that it happens on particular devices:
The funny bit is that the Galaxy S9+ and the Nexus 6 we use internally for testing so we know that most of the time it is working fine. It doesn't seem related to the underlying OS, seems to be a bug in the libs themselves. |
Thanks for the information. Can you also share your dependencies from the build.gradle file? |
Hey @dimipaun. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 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. @dimipaun 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. |
We keep seeing this error in Crashlytics:
The text was updated successfully, but these errors were encountered: