dependencies {
    compile 'com.google.android.gms:play-services-maps:11.8.0'
    compile 'com.google.android.gms:play-services-auth:11.8.0'
    compile 'com.google.android.gms:play-services-ads:11.8.0'
    compile 'com.google.firebase:firebase-storage:11.8.0'

}
apply plugin: 'com.google.gms.google-services'


// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    repositories {


        maven { url 'https://maven.fabric.io/public' }

        jcenter()
        google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.0'
        classpath 'com.google.gms:google-services:3.1.1'


        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

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

我尝试了所有的方法，但没有一种对我有效。更改gradle版本对我来说很有效。

我在gradle-wrapper.properties中更改了以下内容

from

distributionUrl=https\://services.gradle.org/distributions/gradle-6.1.1-all.zip

to

distributionUrl=https\://services.gradle.org/distributions/gradle-6.3-all.zip

进入Android SDK管理器，安装以下两个库的最新版本

谷歌播放服务 谷歌库

错误:(30,13)Failed to resolve: com.google.firebase:firebase-auth:9.6.1

如果你遇到这个错误，并且你使用的是Android studio 2.2，其中集成了firebase组件，默认的库版本为9.6.0，你正在添加9.6.1等最新的依赖项。您可能需要将com.google.firebase:firebase-auth:9.6.1降级为com.google.firebase:firebase-auth:9.6.0

或者检查您预先安装的firebase的库版本，并确保它与您试图添加或添加到项目中的新库版本相同。

如果使用命令行工具，请执行

sdkmanager 'extras;google;m2repository'
sdkmanager 'extras;android;m2repository'

面对我自己，在评论中看到过几次类似的问题-即使安装了“最新”谷歌播放服务和谷歌存储库仍然有同样的问题。

问题是，它们可能是当前Android SDK工具版本的最新版本，但不是应用构建所需的最新版本。

In such case make sure to install latest version of Android SDK Tools first, and probably Android SDK Platform-tools (both under Tools branch). Also please note you may need to go through this several times if you haven't updated for a long time (i.e. install latest Android SDK Tools and Android SDK Platform-tools, then restart Android SDK Manager, then repeat), since the updates seem to be going through some critical mandatory milestones and you cannot install the very latest if you currently have the revision which is pretty "old".