-
Notifications
You must be signed in to change notification settings - Fork 578
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
google-services:4.3.9 breaks firebase #2894
Comments
I found a few problems with this issue:
|
Same here. Reverted back to previous version. |
I have lost precious 6 hours of my life for this problem -.- |
Last night I didn't understand what happened, until compare with another project. :( I lost much time |
for what I can see in my project, the plugin does not generate the resources in the |
same error! what is solution ? |
It looks like the 4.3.9 is having multiple issues. The official docs still say 4.3.8, so I'd suggest reverting back to .8 for now. Thanks |
Got the same problem today after updating google-services to 4.3.9. Reverting to 4.3.8 fixes the initialization.
|
Got the same error. Is there any solution for this |
A fix is on the way and will be deployed as 4.3.10, for now use 4.3.8 |
google-services-plugin 4.3.10 is now live and should fix the above issue, please re-open if this is not the case. |
Confirmed. Fixed for me. Thank you for the quick turnaround. |
Damn I have been trying to figure out what am I doing wrong and now here I am finding this :) |
I could generate the values.xml on 4.3.8 and as soon as I update it to 4.3.10 the file doesn't get generated. I tried to clean/rebuild and invalidate caches and restart, but I still cannot generate the values.xml file. Please help me resolve the issue. |
Android app
My root build.gradle.kts contains
I updated today com.google.gms:google-services:4.3.8 to com.google.gms:google-services:4.3.9 and my android app crashes on launch now due to firebase.
If I revert back from .9 to .8, then everything works again.
Not sure if it's a firebase issue or a google-services issue, but I figured I'd be proactive.
The text was updated successfully, but these errors were encountered: