Skip to content
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

Android build fails because it suddenly can't find com.google.gms:google-services:4.1.0 #969

Closed
phal0r opened this issue Dec 10, 2018 · 2 comments

Comments

@phal0r
Copy link

phal0r commented Dec 10, 2018

Describe the bug
Without any prior changes, the Android build fails since today.

To Reproduce
Normal install

Expected behavior
Build should just run smoothly-

Plugin Version
2.0.5 (latest release)

Additional context
I just want to replicate the issue from another hybrid plugin for firebase:
EddyVerbruggen/nativescript-plugin-firebase#1072

explanation: TL;DR: Google unpublished the dependency from their maven repo, so we need to have the plugin add another maven repo during the build.

There they suggest to change the repos. I think the same needs to be done here aswell.

@zabaat
Copy link

zabaat commented Dec 11, 2018

Did you try the suggestion at the bottom of the readme:

Google Play Services
Your build may fail if you are installing multiple plugins that use Google Play Services. This is caused by the plugins installing different versions of the Google Play Services library. This can be resolved by installing cordova-android-play-services-gradle-release.

If your build is still failing, you can try installing cordova-android-firebase-gradle-release. For more info, read the following comment about locking down the specific versions for play services and firebase. It is suggested to use + instead of 15.+ to ensure the correct versions are used.

@phal0r
Copy link
Author

phal0r commented Dec 11, 2018

@zabaat
Thanks for your answer. This is not a problem with dependency conflicts, but google accidently depublished some dependencies necessary for firebase, thus giving build errors. This mistake was aknowlegeded and is now fixed.

Here is an official statement: https://issuetracker.google.com/issues/120759347#comment36

Since it is resolved by google I will close this now.

@phal0r phal0r closed this as completed Dec 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants