Error: could not find com.google.gms:google-services:4.2.0












50














today I was trying to update com.google.gms:google-services to 4.2.0 from 4.1.0 as it's the latest version and recommended by firebase. But I get this error:



Could not find com.google.gms:google-services:4.2.0.
Searched in the following locations:
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
Required by:
project :


And here is my project's build gradle:



// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
google()
maven {
url 'https://maven.fabric.io/public'
}
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'

classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
// These docs use an open ended version so that our plugin
// can be updated quickly in response to Android tooling updates

// We recommend changing it to the latest version from our changelog:
// https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
classpath 'io.fabric.tools:gradle:1.27.0'
}
}

allprojects {
repositories {
jcenter()
maven {
url 'https://maven.google.com/'
}
google()
}
}


UPDATE:



As Doug Stevenson said the dependency is now up and running so just use google() in your repositories.



If you have any problems with other google repositories (firebase, exoplayer) you can track the issue progress here.










share|improve this question
























  • I think there is some issue with google-services same question is asked here by different user question links are here 1 2
    – Nilesh Rathod
    Dec 10 at 13:24








  • 1




    stackoverflow.com/questions/53704155/…
    – Nilesh Rathod
    Dec 10 at 13:26










  • Try this adding this repository: stackoverflow.com/a/53704634/752781
    – pandre
    Dec 10 at 14:09










  • issuetracker.google.com/issues/120759347
    – Steve
    Dec 10 at 16:49










  • This issue is resolved now if you use google() in your buildscript dependencies.
    – Doug Stevenson
    Dec 10 at 21:23
















50














today I was trying to update com.google.gms:google-services to 4.2.0 from 4.1.0 as it's the latest version and recommended by firebase. But I get this error:



Could not find com.google.gms:google-services:4.2.0.
Searched in the following locations:
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
Required by:
project :


And here is my project's build gradle:



// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
google()
maven {
url 'https://maven.fabric.io/public'
}
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'

classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
// These docs use an open ended version so that our plugin
// can be updated quickly in response to Android tooling updates

// We recommend changing it to the latest version from our changelog:
// https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
classpath 'io.fabric.tools:gradle:1.27.0'
}
}

allprojects {
repositories {
jcenter()
maven {
url 'https://maven.google.com/'
}
google()
}
}


UPDATE:



As Doug Stevenson said the dependency is now up and running so just use google() in your repositories.



If you have any problems with other google repositories (firebase, exoplayer) you can track the issue progress here.










share|improve this question
























  • I think there is some issue with google-services same question is asked here by different user question links are here 1 2
    – Nilesh Rathod
    Dec 10 at 13:24








  • 1




    stackoverflow.com/questions/53704155/…
    – Nilesh Rathod
    Dec 10 at 13:26










  • Try this adding this repository: stackoverflow.com/a/53704634/752781
    – pandre
    Dec 10 at 14:09










  • issuetracker.google.com/issues/120759347
    – Steve
    Dec 10 at 16:49










  • This issue is resolved now if you use google() in your buildscript dependencies.
    – Doug Stevenson
    Dec 10 at 21:23














50












50








50


5





today I was trying to update com.google.gms:google-services to 4.2.0 from 4.1.0 as it's the latest version and recommended by firebase. But I get this error:



Could not find com.google.gms:google-services:4.2.0.
Searched in the following locations:
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
Required by:
project :


And here is my project's build gradle:



// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
google()
maven {
url 'https://maven.fabric.io/public'
}
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'

classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
// These docs use an open ended version so that our plugin
// can be updated quickly in response to Android tooling updates

// We recommend changing it to the latest version from our changelog:
// https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
classpath 'io.fabric.tools:gradle:1.27.0'
}
}

allprojects {
repositories {
jcenter()
maven {
url 'https://maven.google.com/'
}
google()
}
}


UPDATE:



As Doug Stevenson said the dependency is now up and running so just use google() in your repositories.



If you have any problems with other google repositories (firebase, exoplayer) you can track the issue progress here.










share|improve this question















today I was trying to update com.google.gms:google-services to 4.2.0 from 4.1.0 as it's the latest version and recommended by firebase. But I get this error:



Could not find com.google.gms:google-services:4.2.0.
Searched in the following locations:
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://jcenter.bintray.com/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://dl.google.com/dl/android/maven2/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.pom
https://maven.fabric.io/public/com/google/gms/google-services/4.2.0/google-services-4.2.0.jar
Required by:
project :


And here is my project's build gradle:



// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
google()
maven {
url 'https://maven.fabric.io/public'
}
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'

classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
// These docs use an open ended version so that our plugin
// can be updated quickly in response to Android tooling updates

// We recommend changing it to the latest version from our changelog:
// https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
classpath 'io.fabric.tools:gradle:1.27.0'
}
}

allprojects {
repositories {
jcenter()
maven {
url 'https://maven.google.com/'
}
google()
}
}


UPDATE:



As Doug Stevenson said the dependency is now up and running so just use google() in your repositories.



If you have any problems with other google repositories (firebase, exoplayer) you can track the issue progress here.







android firebase android-studio android-gradle jcenter






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 11 at 9:09

























asked Dec 10 at 13:20









Martynas Jegorovas

26829




26829












  • I think there is some issue with google-services same question is asked here by different user question links are here 1 2
    – Nilesh Rathod
    Dec 10 at 13:24








  • 1




    stackoverflow.com/questions/53704155/…
    – Nilesh Rathod
    Dec 10 at 13:26










  • Try this adding this repository: stackoverflow.com/a/53704634/752781
    – pandre
    Dec 10 at 14:09










  • issuetracker.google.com/issues/120759347
    – Steve
    Dec 10 at 16:49










  • This issue is resolved now if you use google() in your buildscript dependencies.
    – Doug Stevenson
    Dec 10 at 21:23


















  • I think there is some issue with google-services same question is asked here by different user question links are here 1 2
    – Nilesh Rathod
    Dec 10 at 13:24








  • 1




    stackoverflow.com/questions/53704155/…
    – Nilesh Rathod
    Dec 10 at 13:26










  • Try this adding this repository: stackoverflow.com/a/53704634/752781
    – pandre
    Dec 10 at 14:09










  • issuetracker.google.com/issues/120759347
    – Steve
    Dec 10 at 16:49










  • This issue is resolved now if you use google() in your buildscript dependencies.
    – Doug Stevenson
    Dec 10 at 21:23
















I think there is some issue with google-services same question is asked here by different user question links are here 1 2
– Nilesh Rathod
Dec 10 at 13:24






I think there is some issue with google-services same question is asked here by different user question links are here 1 2
– Nilesh Rathod
Dec 10 at 13:24






1




1




stackoverflow.com/questions/53704155/…
– Nilesh Rathod
Dec 10 at 13:26




stackoverflow.com/questions/53704155/…
– Nilesh Rathod
Dec 10 at 13:26












Try this adding this repository: stackoverflow.com/a/53704634/752781
– pandre
Dec 10 at 14:09




Try this adding this repository: stackoverflow.com/a/53704634/752781
– pandre
Dec 10 at 14:09












issuetracker.google.com/issues/120759347
– Steve
Dec 10 at 16:49




issuetracker.google.com/issues/120759347
– Steve
Dec 10 at 16:49












This issue is resolved now if you use google() in your buildscript dependencies.
– Doug Stevenson
Dec 10 at 21:23




This issue is resolved now if you use google() in your buildscript dependencies.
– Doug Stevenson
Dec 10 at 21:23












4 Answers
4






active

oldest

votes


















23














Because google-services:4.2.0 is not available at Central Repository, so it needs to be downloaded from Android Tools Repository. To add this to your project add



maven { url 'https://dl.bintray.com/android/android-tools' }


this to buildscript repositories. For more refer to https://mvnrepository.com/artifact/com.google.gms/google-services/4.2.0



buildscript {
repositories {
jcenter()
google()
maven {
url 'https://maven.fabric.io/public'
}
// Add this to your project
maven { url 'https://dl.bintray.com/android/android-tools' }
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'

classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
// These docs use an open ended version so that our plugin
// can be updated quickly in response to Android tooling updates

// We recommend changing it to the latest version from our changelog:
// https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
classpath 'io.fabric.tools:gradle:1.27.0'
}
}

allprojects {
repositories {
jcenter()
maven {
url 'https://maven.google.com/'
}
google()
}
}





share|improve this answer





















  • Thanks. Any idea when it will be available in Central Repository?
    – Martynas Jegorovas
    Dec 10 at 14:42






  • 1




    Sorry, no idea about that in Central Repository latest version is 3.11.
    – Deepanshu tyagi
    Dec 10 at 14:47






  • 5




    This is only a short term fix. There is currently something wrong with the Google maven repo. It's being investigated. In the long term, you should depend on using google() in your build.gradle.
    – Doug Stevenson
    Dec 10 at 16:08










  • Thanks for the heads up @DougStevenson!
    – Elliott
    Dec 10 at 16:46



















34














Monday December 10 2018, 1:30PM PST



The Google Play services plugin, the Firebase Performance monitoring plug, exoplayer, and possible other dependencies were found to be missing on jCenter. It's not clear why, but some of the teams are known to be moving their build artifacts to the Google maven repo.



As of right now, the Google Play services plugin has been migrated, and should be available through google() in your buildscript for now.






share|improve this answer



















  • 3




    Thanks for the answer. Hope the problem is fixed as soon as possible!
    – Martynas Jegorovas
    Dec 10 at 16:18










  • Thanks! Indeed, good luck with the fix! We are using the bintray one temporarily.
    – Archison
    Dec 10 at 16:37






  • 1




    Is there somewhere we can monitor the status of this?
    – Mike
    Dec 10 at 17:08






  • 14




    issuetracker.google.com/issues/120759347
    – Hugo Gresse
    Dec 10 at 17:17



















5














Try this, work for me:



buildscript {
repositories {
google()
//jcenter()
jcenter {url 'https://dl.bintray.com/android/android-tools'}
jcenter {url 'https://firebase.bintray.com/gradle'}
mavenCentral ()
}
dependencies {
classpath 'com.android.tools.build:gradle:3.2.1'
classpath 'com.google.gms:google-services:4.2.0'
classpath 'com.google.firebase:firebase-plugins:1.1.5'
}
}

allprojects {
repositories {
google()
//jcenter()
jcenter {url 'https://dl.bintray.com/android/android-tools'}
jcenter {url 'https://firebase.bintray.com/gradle'}
mavenCentral ()

}
}

task clean(type: Delete) {
delete rootProject.buildDir
}





share|improve this answer































    4














    google-services:4.2.0 is now back on google maven repository, just sync gradle with default config:



    allprojects {
    repositories {
    google()
    jcenter()
    }
    }





    share|improve this answer





















      Your Answer






      StackExchange.ifUsing("editor", function () {
      StackExchange.using("externalEditor", function () {
      StackExchange.using("snippets", function () {
      StackExchange.snippets.init();
      });
      });
      }, "code-snippets");

      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "1"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53706565%2ferror-could-not-find-com-google-gmsgoogle-services4-2-0%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      23














      Because google-services:4.2.0 is not available at Central Repository, so it needs to be downloaded from Android Tools Repository. To add this to your project add



      maven { url 'https://dl.bintray.com/android/android-tools' }


      this to buildscript repositories. For more refer to https://mvnrepository.com/artifact/com.google.gms/google-services/4.2.0



      buildscript {
      repositories {
      jcenter()
      google()
      maven {
      url 'https://maven.fabric.io/public'
      }
      // Add this to your project
      maven { url 'https://dl.bintray.com/android/android-tools' }
      }
      dependencies {
      classpath 'com.android.tools.build:gradle:3.2.1'
      classpath 'com.google.gms:google-services:4.2.0'

      classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
      classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
      // These docs use an open ended version so that our plugin
      // can be updated quickly in response to Android tooling updates

      // We recommend changing it to the latest version from our changelog:
      // https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
      classpath 'io.fabric.tools:gradle:1.27.0'
      }
      }

      allprojects {
      repositories {
      jcenter()
      maven {
      url 'https://maven.google.com/'
      }
      google()
      }
      }





      share|improve this answer





















      • Thanks. Any idea when it will be available in Central Repository?
        – Martynas Jegorovas
        Dec 10 at 14:42






      • 1




        Sorry, no idea about that in Central Repository latest version is 3.11.
        – Deepanshu tyagi
        Dec 10 at 14:47






      • 5




        This is only a short term fix. There is currently something wrong with the Google maven repo. It's being investigated. In the long term, you should depend on using google() in your build.gradle.
        – Doug Stevenson
        Dec 10 at 16:08










      • Thanks for the heads up @DougStevenson!
        – Elliott
        Dec 10 at 16:46
















      23














      Because google-services:4.2.0 is not available at Central Repository, so it needs to be downloaded from Android Tools Repository. To add this to your project add



      maven { url 'https://dl.bintray.com/android/android-tools' }


      this to buildscript repositories. For more refer to https://mvnrepository.com/artifact/com.google.gms/google-services/4.2.0



      buildscript {
      repositories {
      jcenter()
      google()
      maven {
      url 'https://maven.fabric.io/public'
      }
      // Add this to your project
      maven { url 'https://dl.bintray.com/android/android-tools' }
      }
      dependencies {
      classpath 'com.android.tools.build:gradle:3.2.1'
      classpath 'com.google.gms:google-services:4.2.0'

      classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
      classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
      // These docs use an open ended version so that our plugin
      // can be updated quickly in response to Android tooling updates

      // We recommend changing it to the latest version from our changelog:
      // https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
      classpath 'io.fabric.tools:gradle:1.27.0'
      }
      }

      allprojects {
      repositories {
      jcenter()
      maven {
      url 'https://maven.google.com/'
      }
      google()
      }
      }





      share|improve this answer





















      • Thanks. Any idea when it will be available in Central Repository?
        – Martynas Jegorovas
        Dec 10 at 14:42






      • 1




        Sorry, no idea about that in Central Repository latest version is 3.11.
        – Deepanshu tyagi
        Dec 10 at 14:47






      • 5




        This is only a short term fix. There is currently something wrong with the Google maven repo. It's being investigated. In the long term, you should depend on using google() in your build.gradle.
        – Doug Stevenson
        Dec 10 at 16:08










      • Thanks for the heads up @DougStevenson!
        – Elliott
        Dec 10 at 16:46














      23












      23








      23






      Because google-services:4.2.0 is not available at Central Repository, so it needs to be downloaded from Android Tools Repository. To add this to your project add



      maven { url 'https://dl.bintray.com/android/android-tools' }


      this to buildscript repositories. For more refer to https://mvnrepository.com/artifact/com.google.gms/google-services/4.2.0



      buildscript {
      repositories {
      jcenter()
      google()
      maven {
      url 'https://maven.fabric.io/public'
      }
      // Add this to your project
      maven { url 'https://dl.bintray.com/android/android-tools' }
      }
      dependencies {
      classpath 'com.android.tools.build:gradle:3.2.1'
      classpath 'com.google.gms:google-services:4.2.0'

      classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
      classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
      // These docs use an open ended version so that our plugin
      // can be updated quickly in response to Android tooling updates

      // We recommend changing it to the latest version from our changelog:
      // https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
      classpath 'io.fabric.tools:gradle:1.27.0'
      }
      }

      allprojects {
      repositories {
      jcenter()
      maven {
      url 'https://maven.google.com/'
      }
      google()
      }
      }





      share|improve this answer












      Because google-services:4.2.0 is not available at Central Repository, so it needs to be downloaded from Android Tools Repository. To add this to your project add



      maven { url 'https://dl.bintray.com/android/android-tools' }


      this to buildscript repositories. For more refer to https://mvnrepository.com/artifact/com.google.gms/google-services/4.2.0



      buildscript {
      repositories {
      jcenter()
      google()
      maven {
      url 'https://maven.fabric.io/public'
      }
      // Add this to your project
      maven { url 'https://dl.bintray.com/android/android-tools' }
      }
      dependencies {
      classpath 'com.android.tools.build:gradle:3.2.1'
      classpath 'com.google.gms:google-services:4.2.0'

      classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.8.4'
      classpath 'com.github.dcendents:android-maven-gradle-plugin:2.1'
      // These docs use an open ended version so that our plugin
      // can be updated quickly in response to Android tooling updates

      // We recommend changing it to the latest version from our changelog:
      // https://docs.fabric.io/android/changelog.html#fabric-gradle-plugin
      classpath 'io.fabric.tools:gradle:1.27.0'
      }
      }

      allprojects {
      repositories {
      jcenter()
      maven {
      url 'https://maven.google.com/'
      }
      google()
      }
      }






      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Dec 10 at 14:22









      Deepanshu tyagi

      25426




      25426












      • Thanks. Any idea when it will be available in Central Repository?
        – Martynas Jegorovas
        Dec 10 at 14:42






      • 1




        Sorry, no idea about that in Central Repository latest version is 3.11.
        – Deepanshu tyagi
        Dec 10 at 14:47






      • 5




        This is only a short term fix. There is currently something wrong with the Google maven repo. It's being investigated. In the long term, you should depend on using google() in your build.gradle.
        – Doug Stevenson
        Dec 10 at 16:08










      • Thanks for the heads up @DougStevenson!
        – Elliott
        Dec 10 at 16:46


















      • Thanks. Any idea when it will be available in Central Repository?
        – Martynas Jegorovas
        Dec 10 at 14:42






      • 1




        Sorry, no idea about that in Central Repository latest version is 3.11.
        – Deepanshu tyagi
        Dec 10 at 14:47






      • 5




        This is only a short term fix. There is currently something wrong with the Google maven repo. It's being investigated. In the long term, you should depend on using google() in your build.gradle.
        – Doug Stevenson
        Dec 10 at 16:08










      • Thanks for the heads up @DougStevenson!
        – Elliott
        Dec 10 at 16:46
















      Thanks. Any idea when it will be available in Central Repository?
      – Martynas Jegorovas
      Dec 10 at 14:42




      Thanks. Any idea when it will be available in Central Repository?
      – Martynas Jegorovas
      Dec 10 at 14:42




      1




      1




      Sorry, no idea about that in Central Repository latest version is 3.11.
      – Deepanshu tyagi
      Dec 10 at 14:47




      Sorry, no idea about that in Central Repository latest version is 3.11.
      – Deepanshu tyagi
      Dec 10 at 14:47




      5




      5




      This is only a short term fix. There is currently something wrong with the Google maven repo. It's being investigated. In the long term, you should depend on using google() in your build.gradle.
      – Doug Stevenson
      Dec 10 at 16:08




      This is only a short term fix. There is currently something wrong with the Google maven repo. It's being investigated. In the long term, you should depend on using google() in your build.gradle.
      – Doug Stevenson
      Dec 10 at 16:08












      Thanks for the heads up @DougStevenson!
      – Elliott
      Dec 10 at 16:46




      Thanks for the heads up @DougStevenson!
      – Elliott
      Dec 10 at 16:46













      34














      Monday December 10 2018, 1:30PM PST



      The Google Play services plugin, the Firebase Performance monitoring plug, exoplayer, and possible other dependencies were found to be missing on jCenter. It's not clear why, but some of the teams are known to be moving their build artifacts to the Google maven repo.



      As of right now, the Google Play services plugin has been migrated, and should be available through google() in your buildscript for now.






      share|improve this answer



















      • 3




        Thanks for the answer. Hope the problem is fixed as soon as possible!
        – Martynas Jegorovas
        Dec 10 at 16:18










      • Thanks! Indeed, good luck with the fix! We are using the bintray one temporarily.
        – Archison
        Dec 10 at 16:37






      • 1




        Is there somewhere we can monitor the status of this?
        – Mike
        Dec 10 at 17:08






      • 14




        issuetracker.google.com/issues/120759347
        – Hugo Gresse
        Dec 10 at 17:17
















      34














      Monday December 10 2018, 1:30PM PST



      The Google Play services plugin, the Firebase Performance monitoring plug, exoplayer, and possible other dependencies were found to be missing on jCenter. It's not clear why, but some of the teams are known to be moving their build artifacts to the Google maven repo.



      As of right now, the Google Play services plugin has been migrated, and should be available through google() in your buildscript for now.






      share|improve this answer



















      • 3




        Thanks for the answer. Hope the problem is fixed as soon as possible!
        – Martynas Jegorovas
        Dec 10 at 16:18










      • Thanks! Indeed, good luck with the fix! We are using the bintray one temporarily.
        – Archison
        Dec 10 at 16:37






      • 1




        Is there somewhere we can monitor the status of this?
        – Mike
        Dec 10 at 17:08






      • 14




        issuetracker.google.com/issues/120759347
        – Hugo Gresse
        Dec 10 at 17:17














      34












      34








      34






      Monday December 10 2018, 1:30PM PST



      The Google Play services plugin, the Firebase Performance monitoring plug, exoplayer, and possible other dependencies were found to be missing on jCenter. It's not clear why, but some of the teams are known to be moving their build artifacts to the Google maven repo.



      As of right now, the Google Play services plugin has been migrated, and should be available through google() in your buildscript for now.






      share|improve this answer














      Monday December 10 2018, 1:30PM PST



      The Google Play services plugin, the Firebase Performance monitoring plug, exoplayer, and possible other dependencies were found to be missing on jCenter. It's not clear why, but some of the teams are known to be moving their build artifacts to the Google maven repo.



      As of right now, the Google Play services plugin has been migrated, and should be available through google() in your buildscript for now.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Dec 10 at 21:22

























      answered Dec 10 at 16:07









      Doug Stevenson

      69.3k880101




      69.3k880101








      • 3




        Thanks for the answer. Hope the problem is fixed as soon as possible!
        – Martynas Jegorovas
        Dec 10 at 16:18










      • Thanks! Indeed, good luck with the fix! We are using the bintray one temporarily.
        – Archison
        Dec 10 at 16:37






      • 1




        Is there somewhere we can monitor the status of this?
        – Mike
        Dec 10 at 17:08






      • 14




        issuetracker.google.com/issues/120759347
        – Hugo Gresse
        Dec 10 at 17:17














      • 3




        Thanks for the answer. Hope the problem is fixed as soon as possible!
        – Martynas Jegorovas
        Dec 10 at 16:18










      • Thanks! Indeed, good luck with the fix! We are using the bintray one temporarily.
        – Archison
        Dec 10 at 16:37






      • 1




        Is there somewhere we can monitor the status of this?
        – Mike
        Dec 10 at 17:08






      • 14




        issuetracker.google.com/issues/120759347
        – Hugo Gresse
        Dec 10 at 17:17








      3




      3




      Thanks for the answer. Hope the problem is fixed as soon as possible!
      – Martynas Jegorovas
      Dec 10 at 16:18




      Thanks for the answer. Hope the problem is fixed as soon as possible!
      – Martynas Jegorovas
      Dec 10 at 16:18












      Thanks! Indeed, good luck with the fix! We are using the bintray one temporarily.
      – Archison
      Dec 10 at 16:37




      Thanks! Indeed, good luck with the fix! We are using the bintray one temporarily.
      – Archison
      Dec 10 at 16:37




      1




      1




      Is there somewhere we can monitor the status of this?
      – Mike
      Dec 10 at 17:08




      Is there somewhere we can monitor the status of this?
      – Mike
      Dec 10 at 17:08




      14




      14




      issuetracker.google.com/issues/120759347
      – Hugo Gresse
      Dec 10 at 17:17




      issuetracker.google.com/issues/120759347
      – Hugo Gresse
      Dec 10 at 17:17











      5














      Try this, work for me:



      buildscript {
      repositories {
      google()
      //jcenter()
      jcenter {url 'https://dl.bintray.com/android/android-tools'}
      jcenter {url 'https://firebase.bintray.com/gradle'}
      mavenCentral ()
      }
      dependencies {
      classpath 'com.android.tools.build:gradle:3.2.1'
      classpath 'com.google.gms:google-services:4.2.0'
      classpath 'com.google.firebase:firebase-plugins:1.1.5'
      }
      }

      allprojects {
      repositories {
      google()
      //jcenter()
      jcenter {url 'https://dl.bintray.com/android/android-tools'}
      jcenter {url 'https://firebase.bintray.com/gradle'}
      mavenCentral ()

      }
      }

      task clean(type: Delete) {
      delete rootProject.buildDir
      }





      share|improve this answer




























        5














        Try this, work for me:



        buildscript {
        repositories {
        google()
        //jcenter()
        jcenter {url 'https://dl.bintray.com/android/android-tools'}
        jcenter {url 'https://firebase.bintray.com/gradle'}
        mavenCentral ()
        }
        dependencies {
        classpath 'com.android.tools.build:gradle:3.2.1'
        classpath 'com.google.gms:google-services:4.2.0'
        classpath 'com.google.firebase:firebase-plugins:1.1.5'
        }
        }

        allprojects {
        repositories {
        google()
        //jcenter()
        jcenter {url 'https://dl.bintray.com/android/android-tools'}
        jcenter {url 'https://firebase.bintray.com/gradle'}
        mavenCentral ()

        }
        }

        task clean(type: Delete) {
        delete rootProject.buildDir
        }





        share|improve this answer


























          5












          5








          5






          Try this, work for me:



          buildscript {
          repositories {
          google()
          //jcenter()
          jcenter {url 'https://dl.bintray.com/android/android-tools'}
          jcenter {url 'https://firebase.bintray.com/gradle'}
          mavenCentral ()
          }
          dependencies {
          classpath 'com.android.tools.build:gradle:3.2.1'
          classpath 'com.google.gms:google-services:4.2.0'
          classpath 'com.google.firebase:firebase-plugins:1.1.5'
          }
          }

          allprojects {
          repositories {
          google()
          //jcenter()
          jcenter {url 'https://dl.bintray.com/android/android-tools'}
          jcenter {url 'https://firebase.bintray.com/gradle'}
          mavenCentral ()

          }
          }

          task clean(type: Delete) {
          delete rootProject.buildDir
          }





          share|improve this answer














          Try this, work for me:



          buildscript {
          repositories {
          google()
          //jcenter()
          jcenter {url 'https://dl.bintray.com/android/android-tools'}
          jcenter {url 'https://firebase.bintray.com/gradle'}
          mavenCentral ()
          }
          dependencies {
          classpath 'com.android.tools.build:gradle:3.2.1'
          classpath 'com.google.gms:google-services:4.2.0'
          classpath 'com.google.firebase:firebase-plugins:1.1.5'
          }
          }

          allprojects {
          repositories {
          google()
          //jcenter()
          jcenter {url 'https://dl.bintray.com/android/android-tools'}
          jcenter {url 'https://firebase.bintray.com/gradle'}
          mavenCentral ()

          }
          }

          task clean(type: Delete) {
          delete rootProject.buildDir
          }






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 10 at 16:46

























          answered Dec 10 at 16:07









          Novian Agung

          814




          814























              4














              google-services:4.2.0 is now back on google maven repository, just sync gradle with default config:



              allprojects {
              repositories {
              google()
              jcenter()
              }
              }





              share|improve this answer


























                4














                google-services:4.2.0 is now back on google maven repository, just sync gradle with default config:



                allprojects {
                repositories {
                google()
                jcenter()
                }
                }





                share|improve this answer
























                  4












                  4








                  4






                  google-services:4.2.0 is now back on google maven repository, just sync gradle with default config:



                  allprojects {
                  repositories {
                  google()
                  jcenter()
                  }
                  }





                  share|improve this answer












                  google-services:4.2.0 is now back on google maven repository, just sync gradle with default config:



                  allprojects {
                  repositories {
                  google()
                  jcenter()
                  }
                  }






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 10 at 20:59









                  Hani

                  4111




                  4111






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Stack Overflow!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53706565%2ferror-could-not-find-com-google-gmsgoogle-services4-2-0%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                      Mangá

                      Eduardo VII do Reino Unido