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
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 }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") }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:assembleDebug04
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.
- from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
- from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.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.See scope and start
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)