-
Notifications
You must be signed in to change notification settings - Fork 588
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
java.lang.NullPointerException - Attempt to invoke virtual method 'int java.util.AbstractCollection.size()' on a null object reference #6628
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
@lehcar09 👋 I see you triaged my issue but didn't answer. This is an actual production bug affecting all of my users so I'd love to get at least a bit of insight of what's going on and if there's something I can do on my end to mitigate this. Many thanks! |
Hi @benoitletondor, I’m currently taking a look at this. Based on your description, this looks like a device specific issue and started on Jan 15. Did you recently update the Firebase version you’re using? Can you share the previous version you’re using? Looking into our release notes, there are no changes in Firebase Authentication in BOM 33.7.0. |
I didn't bump any firebase dependency no, the only I changed is the AGP version from 8.7.3 to 8.8.0 |
This issue might be caused by the incompatibility of the AGP version on Chromebook devices running Android 11. Could you share your gradle app/module file? Aside from that, have you tried reverting to AGP 8.7.3 to see if the error rate reduces? |
[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment
Build #AI-242.23726.103.2422.12816248, built on December 18, 2024
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Crash when calling
com.google.firebase.auth.FirebaseAuth.getInstance()
on Chromebook, exactly like #5735The stack trace:
trace.txt
Seems to happen only on
AMD Stoney Ridge Chromebook
running Android 11The text was updated successfully, but these errors were encountered: