Skip to content Skip to sidebar Skip to footer

All Gms/firebase Libraries Must Use The Exact Same Version Specification Android Studio

I know this question has been asked many time but I couldn't figure this out. Let me explain on 2 may firebase has announced that Firebase Android SDKs now have independent version

Solution 1:

The solution is:

Change your dependency to 12.0.1 and downgrade the gradle plugin to version 3.2.1.

There's a known issue about using google-services 3.3 in multimodule apps. That means downgrading to google-services to 3.2.1 may be your only option until a new version that fixes the bug is released.


Solution 2:

The change was introduced Google Services 3.3. So upgrade your classpath to:

classpath 'com.google.gms:google-services:3.3.0'

Since you're using an older version of Google Services, it still validates the older logic that all versions must be the same.

Also see Doug's blog post on this change: https://android-developers.googleblog.com/2018/05/announcing-new-sdk-versioning.html


Solution 3:

What version of Android Studio are you using? That lint error was from before Google Play services and Firebase libraries could be of different versions. https://developer.android.com/studio/releases/, the latest stable (3.1+) version of Android Studio should exempt all newer Google Play services and Firebase libraries from this check (still checks for versions below 15.0.0)

Blog post has more details: https://android-developers.googleblog.com/2018/05/announcing-new-sdk-versioning.html

This should be unrelated to the version of the google-services plugin used.


Post a Comment for "All Gms/firebase Libraries Must Use The Exact Same Version Specification Android Studio"