Gradle is issuing an error "Could not create plugin of type 'AppPlugin'"

Question

I'm trying to create a simple android project with gradle. I work in a computer with Debian GNU/Linux 7 'wheezy'.

I followed the recomendations in Gradle Plugin User Guide - Android Tools Project Site, but it casts an error:

FAILURE: Build failed with an exception.

* Where:
Build file '/home/alex/Proyectos/MyLogin/build.gradle' line: 11

* What went wrong:
A problem occurred evaluating root project 'MyLogin'.
> Could not create plugin of type 'AppPlugin'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 4.817 secs

I followed the specifications:

Gradle 1.9
Plugin 0.7
SDK 17+ (actually 19)

I also started a project anew, and the results I showed were issued by the command gradle tasks as shown in the documentation.

I also tried gradle 1.10, but the result is the same.

Even this question was not usefull, since it solved with 'upgrading' to gradle 1.6 (I understand that plugin 0.7 requires at least gradle 1.9).

I tried this after failing with the same error in android-studio and IntelliJ Idea.

EDIT: I also tried with new projects in both IDEs, and got the same issue. But what most surprises me is that both IDEs use gradle 1.8 in their wrapped form. I tried to cinfigure both of them to use my local gradle install, but still the same issue.

What am I doing wrong? Is it a bug? How can I avoid the problem?

Please, help me.

EDIT: Here is my build.gradle

buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:0.7.+'
    }
}

apply plugin: 'android'

repositories {
    mavenCentral()
}

android {
    compileSdkVersion 14
    buildToolsVersion '19.0.1'

    defaultConfig {
        minSdkVersion 14
        targetSdkVersion 19
    }
}

sourceCompatibility = 1.6

version = '0.1'

dependencies {
    compile 'com.android.support:support-v4:18.0.0'
    //compile project(':core')
}

Sorry for the ommition of such important data. Here is the `build.gradle`. — aBarocio80, Jan 02 '14 at 18:56
I tried this "build.gradle" - the bug appears under gradle 1.10 and solved by downgrading to 1.9. — akhikhl, Jan 02 '14 at 19:21

score 27 · Accepted Answer · answered Jan 08 '14 at 02:22

27

Google made a mistake with version 0.7.2 of the Gradle plugin:

Note: 0.7.2 requires Java7. This is a mistake. Use 0.7.3 instead.

Release 0.7.3 re-enables Java6 support. Declaring Gradle 0.7.3 in my build files does indeed resolve this for me.

No one is perfect :)

http://tools.android.com/tech-docs/new-build-system

answered Jan 08 '14 at 02:22

Ken

30,811
34
116
155

3

Thanks. I guess it was fixed with the release of 0.7.3. I have it configurated with "0.7.+". – aBarocio80 Jan 12 '14 at 03:54
Glad it is fixed for you. I've stopped using the expression "0.7.+" because 0.6, 0.7.1 and 0.7.2 caused me problems. I now fix on a release - e.g. "0.7.3". – Ken Jan 12 '14 at 04:52
1

Doh! Thank you, damn I'm an ass. – Codeversed Nov 21 '14 at 02:44

score 22 · Answer 2 · edited May 23 '17 at 12:08

22

Use Gradle 1.9 instead of Gradle 1.10. There is an issue with 1.10 : https://code.google.com/p/android/issues/detail?id=63822

Also answered here:

Can't find org.gradle.api.artifacts.result.ResolvedModuleVersionResult when apply Android plugin in Gradle

edited May 23 '17 at 12:08

Community

1
1

answered Dec 28 '13 at 18:14

Vasile Jureschi

2,169
2
17
17

Should have read more carefully, I see you already tried 1.9. – Vasile Jureschi Dec 28 '13 at 18:15
Just what I was looking for. This answer should be 'accepted' – Vladimir Jan 03 '14 at 06:16
OK. It solves the problem. It seems that I had missplaced the version in my PATH environment variable. Thanks a lot. – aBarocio80 Jan 05 '14 at 17:09
Also, for future reference, switching to a newer version of gradle would/should also fix this. – CasualT Jul 08 '15 at 21:31

JJD · Answer 3 · 2014-02-05T17:57:24.937

19

I got it working using Gradle 1.10 with the Gradle plugin 0.8.0.

// /build.gradle
// Top-level build file where you can add configuration 
// options common to all sub-projects/modules.
buildscript {
    repositories {
        mavenCentral()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:0.8.+'
    }
}

...

# /gradle/wrapper/gradle-wrapper.properties.
#Sat Feb 01 20:41:29 CET 2014
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=http\://services.gradle.org/distributions/gradle-1.10-bin.zip

edited Feb 05 '14 at 17:57

answered Feb 01 '14 at 21:26

JJD

50,076
60
203
339

3

Wouldn't it be better to put gradle:0.8.+ instead of gradle:0.8.0? That way you know you're using the latest gradle plugin. – IgorGanapolsky Feb 05 '14 at 15:34
2

@IgorGanapolsy Not necessarily best. For instance, if at the time you had done gradle:0.7.+ you might well have hit problems that are now well-known. The latest is not always the greatest. – Ken Feb 12 '14 at 08:05

score 7 · Answer 4 · answered Jun 10 '15 at 13:06

If you're using the command line to create the project like so:

android create project -g -v 1.2.2 --target 1 --name rtest --path rtest --activity MainActivity --package com.mydomain.rtest

The project is created to use version 1.2.2 of the android-gradle-plugin, but the project is initialised with gradle 1.12, which isn't compatible.

To fix it, do the following:

Open rtest/gradle/wrapper/gradle-wrapper.properties and set distributionUrl to the release you want; for example: http\://services.gradle.org/distributions/gradle-2.2.1-all.zip (don't forget to escape the colon - yes, that makes me smile too);
Open build.gradle and change runProguard false to minifyEnabled false;
./gradlew clean && ./gradlew assembleDebug
I also remove the hidden .gradle folder, but I'm not sure if it's necessary

And it all works again.

thanks! this is the solution that works for me with the latest set of tools. (as of July 2015) — alvi, Jul 12 '15 at 08:44
Thanks! Google is so shamelessly drinking the Kool-aid from Idea, their command line tools are in a sorry state... — Rick77, Jun 14 '19 at 17:38

score 2 · Answer 5 · answered Jul 29 '16 at 07:28

2

For those who are using 2.1 version of studio, replace classpath 'com.android.tools.build:gradle:2.1.0-rc1' with classpath 'com.android.tools.build:gradle:2.1.0'. This solved my problem.

answered Jul 29 '16 at 07:28

Isham

424
4
14

score 1 · Answer 6 · answered Jan 24 '14 at 09:30

1

If you are attempting to update your Gradle 1.9 project to Gradle 1.10 using

task wrapper(type: Wrapper) {
    gradleVersion = '1.10'
}

and command ./gradlew wrapper you will get the same error as above.

Solution is to install Gradle 1.10 onto your machine and upgrade your project not using the wrapper

gradle wrapper

answered Jan 24 '14 at 09:30

Blundell

75,855
30
208
233

Is there any way to download gradle wrapper 1.10 and put that into Android Studio? – IgorGanapolsky Feb 05 '14 at 16:06
you have to do it in a file explorer and avoid ASide – Blundell Feb 05 '14 at 16:22

score 1 · Answer 7 · answered Mar 07 '14 at 04:16

1

You can also get this error if you update your system gradle and forget to update the Android Studio gradle home.

answered Mar 07 '14 at 04:16

Eric Woodruff

6,380
3
36
33

score 0 · Answer 8 · answered May 27 '14 at 22:05

0

I got this today when running gradle assembleRelease. I had installed the Ubuntu default of gradle-1.4. This didn't work, so I tried the latest gradle-1.12 and got the same issue.

Downloading and using gradle-1.10 (and matching my gradle-wrapper.properties file to that version) resolved the issue.

This is with Android Studio 0.5.8.

answered May 27 '14 at 22:05

Splaktar

5,506
5
43
74

Any explanation of the -1? I was sharing a working solution at the time. – Splaktar Feb 04 '15 at 00:04

score 0 · Answer 9 · edited Nov 10 '16 at 08:21

0

Ok i guess android studio has answer for this to get this bug out using GUI,

I had this error like this...

after updating the plugins i was facing another issues while building,

so changes the gradle setting to default as shown in the image,

After this build was successful.

edited Nov 10 '16 at 08:21

m0sa

10,712
4
44
91

answered Jan 21 '16 at 06:51

Pankaj Nimgade

4,529
3
20
30

score 0 · Answer 10 · answered Mar 17 '16 at 05:14

0

Go to dependencies and just change the dependencies classpath to classpath 'com.android.tools.build:gradle:2.0.0-beta6' Rest Gradle will take care. Happy coding :)

answered Mar 17 '16 at 05:14

Abhilash

500
4
13

score 0 · Answer 11 · answered Jul 03 '23 at 12:48

0

1: Run with scan to see detailed cause. 2: In my case it was pointing to a file in cache(c/user/.gradle/cache/jr-9...). 3: I deleted jr-9 folder and it fixed my issue

answered Jul 03 '23 at 12:48

Muhammad Ibrahim

1

Gradle is issuing an error "Could not create plugin of type 'AppPlugin'"

11 Answers11

Linked