Skip to content

Android Firebase build errorAndroid: google-services “fix the version conflict” / “depends on another at an exact version”

An Android build with Firebase fails in the google-services plugin. Old plugin versions stop in :app:processDebugGoogleServices with Please fix the version conflict either by updating the version of the google-services plugin or updating the version of com.google.android.gms. Current versions say In project ‘app’ a resolved Google Play services library dependency depends on another at an exact version …, but isn’t being resolved to that version, followed by a Dependency failing line. Either way, the plugin and your Firebase and Play services libraries disagree on versions.

Short answer

Update the google-services Gradle plugin to the version in Firebase’s Android setup guide first. Then declare Firebase libraries through the Firebase BoM, with no version numbers on the individual libraries, and remove hard-coded versions of com.google.firebase and com.google.android.gms libraries. Read the Dependency failing line to find which library forces an old version. In a Flutter app, also upgrade the FlutterFire packages together.

Why the versions conflict, and the fix

  1. 01

    An old google-services plugin

    The old message names the fix: the plugin is older than the Play services libraries it checks. Raise com.google.gms.google-services to the version Firebase’s Android setup guide shows, then sync and build again.

    // android/settings.gradle.kts (Flutter) or the root build.gradle.kts
    plugins {
        id("com.google.gms.google-services") version "4.5.0" apply false
    }
  2. 02

    Firebase libraries pinned to different versions

    “When you use the Firebase BoM in your app, the BoM automatically pulls in the individual library versions mapped to BoM's version.” Firebase, Firebase Android BoM

    Each Firebase library declared with its own version drifts apart over time. The BoM sets one version for all of them. Remove the version numbers from the individual lines.

    // android/app/build.gradle.kts
    dependencies {
        implementation(platform("com.google.firebase:firebase-bom:35.1.0"))
        implementation("com.google.firebase:firebase-analytics")
        implementation("com.google.firebase:firebase-messaging")
    }
  3. 03

    Another SDK pulls an older Play services library

    An ads, maps or analytics SDK can depend on an older com.google.android.gms library. The error lists the dependencies that lead to the failing artifact. Print the dependency tree to see which SDK it is, then upgrade that SDK.

    cd android
    ./gradlew :app:dependencies --configuration debugCompileClasspath
    # the error’s own suggestion:
    ./gradlew --info :app:assembleDebug
  4. 04

    Turning the check off

    “Behavior exhibited by the library will be unknown.” GitHub, google-services version check (DependencyInspector.java)

    The plugin has a disableVersionCheck switch. It hides the error but leaves the mismatched libraries in the app, so use it only to unblock a build while you fix the versions.

    // android/app/build.gradle.kts (stopgap only)
    googleServices {
        disableVersionCheck = true
    }

Checked against the vendor’s docs on : Firebase: Android BoM (Bill of Materials); Firebase: Add Firebase to your Android project; google/play-services-plugins: version check source.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Related: Firebase “google-services” plugin not found · Gradle “Could not resolve all files” · Firebase “Member not found: verifyExtends” · Google Sign-In fails on Android (error 10)

Questions

More on this error

I use Flutter. Where are these versions set?

Mostly in the FlutterFire plugins, which add the Firebase Android libraries for you. Keep firebase_core and the other FlutterFire packages on current versions together, and remove any Firebase lines you added by hand to android/app/build.gradle.

Which BoM version should I use?

The one in Firebase’s Android setup guide, which lists the current BoM. The 35.1.0 above is the version that guide showed on November 8, 2026.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.