build.gradle中com.google.android.gms版本冲突问题排查求助

Hey there, I know how frustrating it is when you’ve already upgraded your Google Play Services (gms) to the latest version but still hit this error. Let’s walk through the most common fixes that usually resolve this problem:

1. Ensure all gms/firebase dependencies use the same version #

This is the #1 culprit. Even if you updated the main gms dependency, other related libraries (like Maps, Auth, Analytics, Firebase modules) might still be pulling in older versions, causing a silent conflict.

Go through your app-level build.gradle file and make sure every dependency starting with com.google.android.gms: or com.google.firebase: uses the exact same version number. For example:

// Good - all versions match
implementation 'com.google.android.gms:play-services-maps:21.0.1'
implementation 'com.google.android.gms:play-services-auth:21.0.1'
implementation 'com.google.firebase:firebase-analytics:21.2.0'

// Bad - version mismatch triggers conflict
implementation 'com.google.android.gms:play-services-maps:11.8.0'
implementation 'com.google.android.gms:play-services-auth:21.0.1'

2. Update the google-services plugin version #

You mentioned upgrading gms, but did you update the plugin itself? The plugin (in your project-level build.gradle) needs to be compatible with your gms dependency version to work properly.

Check your root build.gradle and update the classpath entry to the latest compatible version:

buildscript {
    dependencies {
        // Update this line to the latest google-services plugin version
        classpath 'com.google.gms:google-services:4.4.0'
    }
}

3. Clean up cached build files #

Gradle caches can sometimes hold onto old dependency references, even after you’ve updated them. Run these steps to wipe the slate clean:

• Execute ./gradlew clean (or gradlew clean on Windows) in your terminal to delete cached build files.
• Go to Android Studio’s File > Sync Project with Gradle Files to refresh dependencies.
• Rebuild your project from scratch.

4. Exclude conflicting implicit dependencies from third-party libraries #

Some third-party SDKs might secretly include old gms versions in their dependencies. You can force them to use your specified version by excluding the conflicting group:

implementation('com.example.thirdparty:some-sdk:2.0.0') {
    // Exclude the old gms dependency from this SDK
    exclude group: 'com.google.android.gms'
}

After adding this, sync your project and check if the conflict is resolved.

5. Verify your Gradle wrapper version #

Older Gradle versions might not support the latest gms plugins or dependencies. Check your gradle/wrapper/gradle-wrapper.properties file and make sure the distribution URL points to a recent Gradle version (compatible with your Android Gradle Plugin and google-services plugin).

内容的提问来源于stack exchange，提问作者Trusted