Gradle Error:Execution failed for task ':app:processDebugGoogleServices'

AndroidGradlebuild.gradle

Android Problem Overview


I am following this link to integrate Google sign-in in my android app.https://developers.google.com/identity/sign-in/android/start-integrating As given in last step on the above given page we have to include dependency

 compile 'com.google.android.gms:play-services-auth:8.3.0' 

in app-level build.gradle file but doing so and building project an error comes saying

Error:Execution failed for task ':app:processDebugGoogleServices'.
> Please fix the version conflict.

build.gradle(Module:app)

apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services'


android {
    compileSdkVersion 23
    buildToolsVersion "23.0.2"

    defaultConfig {
        applicationId "com.brainbreaker.socialbuttons"
        minSdkVersion 16
        targetSdkVersion 23
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile 'com.android.support:appcompat-v7:23.0.1'
    compile 'com.android.support:design:23.0.1'
    compile 'com.google.android.gms:play-services-auth:8.3.0'
}

In the build.gradle file the compile dependency line compile 'com.google.android.gms:play-services-auth:8.3.0' shows error

> All com.google.android.gms libraries must use the exact same version > specification (mixing versions can lead to runtime crashes). Found > versions 8.3.0, 8.1.0. Examples include > com.google.android.gms:play-services-base:8.3.0 and > com.google.android.gms:play-services-measurement:8.1.0 There are some > combinations of libraries, or tools and libraries, that are > incompatible, or can lead to bugs. One such incompatibility is > compiling with a version of the Android support libraries that is not > the latest version (or in particular, a version lower than your > targetSdkVersion.)

Here are the messages of gradle build.

Information:Gradle tasks [clean, :app:generateDebugSources, :app:generateDebugAndroidTestSources, :app:compileDebugSources, :app:compileDebugAndroidTestSources, :social_buttons:generateDebugSources, :social_buttons:generateDebugAndroidTestSources, :social_buttons:compileDebugSources, :social_buttons:compileDebugAndroidTestSources]
:clean UP-TO-DATE
:app:clean
:social_buttons:clean
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareComAndroidSupportAppcompatV72301Library
:app:prepareComAndroidSupportDesign2301Library
:app:prepareComAndroidSupportSupportV42301Library
:app:prepareComGoogleAndroidGmsPlayServicesAds810Library
:app:prepareComGoogleAndroidGmsPlayServicesAnalytics810Library
:app:prepareComGoogleAndroidGmsPlayServicesAppindexing810Library
:app:prepareComGoogleAndroidGmsPlayServicesAuth830Library
:app:prepareComGoogleAndroidGmsPlayServicesBase830Library
:app:prepareComGoogleAndroidGmsPlayServicesBasement830Library
:app:prepareComGoogleAndroidGmsPlayServicesMeasurement810Library
:app:prepareDebugDependencies
:app:compileDebugAidl
:app:compileDebugRenderscript
:app:generateDebugBuildConfig
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets
:app:generateDebugResValues UP-TO-DATE
:app:processDebugGoogleServices
Found com.google.android.gms:play-services-auth:8.3.0, but version 8.1.0 is needed
Found com.google.android.gms:play-services-auth:8.3.0, but version 8.1.0 is needed
Found com.google.android.gms:play-services-auth:8.3.0, but version 8.1.0 is needed
Found com.google.android.gms:play-services-auth:8.3.0, but version 8.1.0 is needed
Found com.google.android.gms:play-services-auth:8.3.0, but version 8.1.0 is needed
:app:processDebugGoogleServices FAILED
Error:Execution failed for task ':app:processDebugGoogleServices'.
> Please fix the version conflict.
Information:BUILD FAILED
Information:Total time: 3.49 secs
Information:1 error
Information:0 warnings
Information:See complete output in console

I am not able to see any way out for this version conflict. Any help is appreciated.

Android Solutions


Solution 1 - Android

I'v got a same issue. but Now I'm fixed.

You should delete a line apply plugin: 'com.google.gms.google-services'

because "com.android.application" package already has same package.

Solution 2 - Android

I had the same issue and resolved it by adding the following line in the dependencies of the project-level build.gradle:

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

For a full working example, check out the following project on github.

Hope this helps :)

Solution 3 - Android

I was finding the same error complaining about mixing google play services version when switching from 8.3 to 8.4. Bizarrely I saw reference to the app-measurement lib which I wasn't using.

I thought maybe one of my app's dependencies was referencing the older version so I ran ./gradlew app:dependencies to find the offending library (non were).

But at the top of task output I found a error message saying that the google plugin could not be found and defaulting to google play services 8.3. I used the sample project @TheYann linked to compare. My setup was identical except I applied the apply plugin: 'com.google.gms.google-services' at the top my app's build.gradle file. I moved to bottom of the file and that fixed the gradle compile error.

Solution 4 - Android

I also faced the same issue. But I forgot to add google-services.json in my project. You can get this file from Google.

Solution 5 - Android

Ensure that you have done these two things under defaultConfig in Android/app/build.gradle after wiring up Firebase for your Flutter app.

  1. Whatever package name you entered while creating your Firebase android project, exactly the same should be updated as your applicationId under defaultConfig.

  2. Add the line multiDexEnabled true under defaultConfig.

So defaultConfig{} should now look something like this

defaultConfig {
    applicationId "com.companyName.appName"
    minSdkVersion 16
    targetSdkVersion 27
    multiDexEnabled true
    versionCode flutterVersionCode.toInteger()
    versionName flutterVersionName
    testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}

Solution 6 - Android

I've solved this problem by deleting the google-services.json file and downloading it again from Firebase console.

Solution 7 - Android

Had the same problem i added compile 'com.google.android.gms:play-services-measurement:8.4.0' and deleted apply plugin: 'com.google.gms.google-services' I was using classpath 'com.google.gms:google-services:2.0.0-alpha6' in the build project.

Solution 8 - Android

In my case when i was using firebase services the google.json file was mismatched check once that also

Solution 9 - Android

I just had to delete and reinstall my google-services.json and then restart Android Studio.

Solution 10 - Android

had the same issue as described by @scottyab.

all references were 8.4.0 but it failed due to a reference to app-measurement 8.3.0 that i did not reference anywhere (but one of the dependencies?). you can see the problem if you hover over the bad(red) dependency in Android Studio. explicitly adding

compile 'com.google.android.gms:play-services-measurement:8.4.0'

to app.gradle solved the issue.

Solution 11 - Android

Important note: You should only apply plugin at bottom of build.gradle (App level)

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

I mistakenly apply this plugin at top of the build.gradle. So I get error.

One more tips : You no need to remove even you use the 3.1.0 or above. Because google not officially announced

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

Solution 12 - Android

Also please check your package name in Manifest and package name in google services json file. If both have package name differ from one another u will have this issue.

Solution 13 - Android

I fixed it without deleting apply plugin: 'com.google.gms.google-services' I had the error Execution failed for task ':app:processDebugGoogleServices' because I was using two different versions of google services in my dependencies :

implementation "com.google.android.gms:play-services-maps:11.8.0"
implementation "com.google.android.gms:play-services-nearby:16.0.0"

I changed it to :

implementation "com.google.android.gms:play-services-maps:11.8.0"
implementation "com.google.android.gms:play-services-nearby:11.8.0"

Then it worked

Solution 14 - Android

When you create an android application in firebase console you should set your application package in future it will be recorded to google-services.json. So this error can happen when you try to add google services in the application which has a different package (Current application package will not match to which was recorded to google-services.json).

Solution 15 - Android

My package name, when creating an application in Firebase, had an underscore '_' in the name.

I mistakenly excluded the underscore. Changing the package name in firebase solved this issue for me.

Solution 16 - Android

I ran into the same issue, I followed the top three steps in this thread. However, I later found that package_name should match with appID in the google-service.json file as well.

Do look at what your package_name says in google.service.json and match it with the actual app id.

Solution 17 - Android

If You are trying to solve this problem for firebase then use this....

Deleting the ** 'com.google.gms.google-services' ** is not the correct way, this problem occurs because of the name changes.

Need to give the same name in the format firebase package name == android package name (check it in /android/app/src/main/AndroidManifest.xml)

Just change the name as android package name then again download the google-services.json then paste it in the /android/app/ like this (/android/app/google-services.json) and run your npm eg. npx react-native run-android It will work 100%.

Solution 18 - Android

I had a similar issue/error.. fixed it by moving apply plugin: 'com.google.gms.google-services'
to the end of app level gradle file.

And updated the version of gms:play-services and gms:play-services auth

Solution 19 - Android

same issue i have.

i tired all possible solutions that i found. but non were worked.

always got this error

Cannot add task ':processDebugGoogleServices' as a task with that name already exists

Now, i solved it.

1) first i checked my config.xml

2) and removed unnecessary plugin. (I used firebase fcm plugin for pushnotification, but there was two unnecessary plugin phonegap-plugin-push and cordova-plugin-customurlscheme. I removed both these plugins)

3) then removed platform.

4) then add platform

5) then build it.

6) now it build successfully.

Solution 20 - Android

Had the same problem with malformed error Deleted the line apply plugin: 'com.google.gms.google-services' And the build got successful

Solution 21 - Android

NEVER DELETE apply plugin: 'com.google.gms.google-services' from the gradle. Sometimes you are using com.google.gms:google-services:3.1.0 , without apply plugin: 'com.google.gms.google-services' your gradle build successfully. BUT IT IS COMPLETELY WRONG !!!! This error comes due to google-service.json file is not at the correct location. Go to your PROJECT TAB at left side above. If you display it as ANDROID make it PROJECT then check your google-service.json file is at this location. EXPAND app then see google-service.json file below the build.gradle. IF NOT PLACE IT THERE BY RIGHT CLICK ON THE app .

Solution 22 - Android

This error comes up when there is change in your config.xml file resulting in mismatching of the data present in google-services.json file. I got it fixed this just by updating changes to my google-services.json file and building the app again ...it worked well.

Solution 23 - Android

If you´re building a new app, put the jsonfile in the right place and make sure it's the jsonfile for that app. Before I realized this, when I clicked the jsonfile, I didn't get the information that wanted.

Go to firebase configurations, download the correct version of google-services.json, and replace the version that didn't work for you. When using the wrong version, you might see the wrong Projectid, storagebucket etc.

Solution 24 - Android

check gradle.properties and add android.useAndroidX=true or you can also add android.enableJetifier=true or you can comment it by #

worked for me

Solution 25 - Android

if you got an error

> Execution failed for task ‘:app:fabricGenerateResourcesDebug’. > Crashlytics Developer Tools error.

remove also this line:

apply plugin: 'io.fabric'

Solution 26 - Android

In my case i have multiple product flavors. It used to work earlier. It stopped working after updating project gradle version to 4.0.1 and 'google-services:4.3.4'.

I got error like 'Task :app:processDebugGoogleServices FAILED' when i run the project.

I replaced 'google-services.json' in app module with 'my-product-flavor/google-services.json'. It is working fine now.

Solution 27 - Android

None of the answers here helped. I needed to have "apply plugin: 'com.google.gms.google-services'" in my gradle. What helped was updating Android Studio to the latest version. I was then able to add the plugin and connect to Firebase Messaging Service.

Solution 28 - Android

What work for me is

add this in build.Gradle(Project)

> dependencies { >
> classpath 'com.google.gms:google-services:3.0.0' > > }

Solution 29 - Android

If you trying to connect to firebase, check if your app package name is the same as what is in google-services JSON file.

"client": [
{
  "client_info": {
    "mobilesdk_app_id": "......",
    "android_client_info": {
      "package_name": "com.something.package"
    }
  }, ...

thanks and good luck.

Solution 30 - Android

Try adding FirebaseAuth even though you don't need it. Don't delete any plugins. This worked for me. Thanks.

Solution 31 - Android

I'v got a same issue. but Now I'm fixed.

You should delete a line apply plugin: 'com.google.gms.google-services'

because "com.android.application" package already has same package.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionbrainbreakerView Question on Stackoverflow
Solution 1 - AndroidseyeonView Answer on Stackoverflow
Solution 2 - AndroidTheYannView Answer on Stackoverflow
Solution 3 - AndroidscottyabView Answer on Stackoverflow
Solution 4 - AndroidThirumalvalavanView Answer on Stackoverflow
Solution 5 - AndroidSunit GautamView Answer on Stackoverflow
Solution 6 - AndroidMarie AmidaView Answer on Stackoverflow
Solution 7 - AndroidMwongera808View Answer on Stackoverflow
Solution 8 - AndroidKamalView Answer on Stackoverflow
Solution 9 - AndroidFosterView Answer on Stackoverflow
Solution 10 - AndroidPhilippView Answer on Stackoverflow
Solution 11 - AndroidRanjithkumarView Answer on Stackoverflow
Solution 12 - AndroidFaheem Ahmad KhanView Answer on Stackoverflow
Solution 13 - AndroidJack'View Answer on Stackoverflow
Solution 14 - AndroidOnregsView Answer on Stackoverflow
Solution 15 - AndroidJacob ZinnView Answer on Stackoverflow
Solution 16 - AndroidManishView Answer on Stackoverflow
Solution 17 - AndroidsanJEEV JEEVaView Answer on Stackoverflow
Solution 18 - AndroidKanishk GuptaView Answer on Stackoverflow
Solution 19 - AndroidHarish MahajanView Answer on Stackoverflow
Solution 20 - AndroidHaris DurraniView Answer on Stackoverflow
Solution 21 - AndroidZzmilanzz ZzmadubashazzView Answer on Stackoverflow
Solution 22 - AndroidGaurav PrasadView Answer on Stackoverflow
Solution 23 - AndroidHappyGView Answer on Stackoverflow
Solution 24 - AndroidRameshView Answer on Stackoverflow
Solution 25 - AndroidAdam SmakaView Answer on Stackoverflow
Solution 26 - AndroidRahulView Answer on Stackoverflow
Solution 27 - Androiduser3079872View Answer on Stackoverflow
Solution 28 - AndroidSamView Answer on Stackoverflow
Solution 29 - AndroidTechlup SolutionsView Answer on Stackoverflow
Solution 30 - AndroidVickyView Answer on Stackoverflow
Solution 31 - AndroidmaharshView Answer on Stackoverflow