Error:(1, 0) Plugin with id 'com.android.application' not found

Question

This is my first attempt at Android Studio. I installed 0.8.0 and updated to 0.8.2. As soon as a project is created I get the error message:

Error:(1, 0) Plugin with id 'com.android.application' not found

C:\Users\Bob\AndroidStudioProjects\HelloAgain6\app\build.gradle

apply plugin: 'com.android.application'

android {
    compileSdkVersion 20
    buildToolsVersion "20.0.0"

    defaultConfig {
        applicationId "com.example.bob.helloagain6"
        minSdkVersion 15
        targetSdkVersion 20
        versionCode 1
        versionName "1.0"
    }
    buildTypes {
        release {
            runProguard false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
}

and C:\Users\Bob\AndroidStudioProjects\HelloAgain6\build.gradle

// Top-level build file where you can add configuration options common to all sub-projects/modules.

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

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        jcenter()
    }
}

I got this problem, but suddenly I see the top level build.gradle was deleted :), so I copy it from git repository and every things goes right — Mehdi Khademloo, Oct 7, 2016 at 20:11
Same thing for me, my build.gradle for project level was moved into the same folder as the wrapper properties during a funky merge so it wasn't finding it at the root where it should be — RESTfulGeoffrey, May 8, 2020 at 11:52
for #FLUTTER projects the solution was to run ./gradlew wrapper in the android directory — Ovidiu Uşvat, Jan 26, 2023 at 11:45

Jared Burrows · Accepted Answer · 2020-12-03 01:33:51Z

494

Updated Answer (Dec. 2, 2020)

Latest Gradle: 6.5

Version check:

./gradlew -v

How to update:

Set URL: ./gradlew wrapper --gradle-version=6.5 --distribution-type=all
Update: ./gradlew wrapper

Latest Android Gradle Plugin: 4.1.0

If you add the following code snippet to the top of your build.gradle file. Gradle will update the build tools.

buildscript {
    repositories {
        google() // For Gradle 4.0+
        maven { url 'https://maven.google.com' } // For Gradle < 4.0
    }

    dependencies {
        classpath 'com.android.tools.build:gradle:4.1.0'
    }
}

Read more here: https://developer.android.com/studio/build/index.html and about version compatibility here: https://developer.android.com/studio/releases/gradle-plugin.html#updating-gradle and https://dl.google.com/dl/android/maven2/index.html.

Original Answer

I had this same error, you need to make sure your Gradle version is compatible with your Android Gradle Plugin.

The latest version of Gradle is 2.0 but you need to use 1.12 in order to use the Android Gradle Plugin.

edited Dec 3, 2020 at 1:33

answered Aug 10, 2014 at 20:30

Jared Burrows

54.8k26 gold badges152 silver badges188 bronze badges

190

+1 for still updating your answer a few months later
– P1nGu1n
Oct 30, 2014 at 21:17
4

@P1nGu1n No problem! It is easier if every sees the most up-to-date information.
– Jared Burrows
Oct 30, 2014 at 21:20
4

@MartinPfeffer No problem. I will continue to keep this updated!
– Jared Burrows
Dec 28, 2014 at 16:51
14

Good answer, though I can't help but wonder why Google would deploy Android Studio like this.. This error is the first thing you see when starting a new project. I mean, what were they thinking!?
– BdR
Mar 27, 2015 at 14:04
17

Android development has many stupid things. Why we should be bothered with all this gradle versions thing
– user25
Aug 6, 2016 at 13:28

| Show 18 more comments

Ash · Accepted Answer · 2014-10-20 10:40:18Z

39

This can happen if you miss adding the Top-level build file.

Just add build.gradle to top level.

It should look like this

// 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.xx.y'
    }
}

allprojects {
    repositories {
        mavenCentral()
    }
}

answered Oct 20, 2014 at 10:40

Ash

1,41116 silver badges20 bronze badges

3

That is exactly what he has.
– Jared Burrows
Mar 20, 2015 at 2:23
What about the existing contents of the file? Just delete them?
– Tom Russell
Aug 8, 2018 at 8:47
1

If you're doing the firebase tutorial you need classpath 'com.android.tools.build:gradle:3.2.1' and classpath 'com.google.gms:google-services:4.0.1'
– jackdaw
Dec 31, 2018 at 12:52

Add a comment |

Md Imran Choudhury · Accepted Answer · 2018-09-23 04:49:47Z

15

In my case, I download the project from GitHub and the Gradle file was missing. So I just create a new project with success build. Then copy-paste the Gradle missing file. And re-build the project is working for me.

answered Sep 23, 2018 at 4:49

Md Imran Choudhury

9,7484 gold badges64 silver badges61 bronze badges

this solved my problem after several hours of trying other methods
– zyz82
Oct 23, 2019 at 21:34
copy the file from where. I also have a missing gradle file, but in my case, its the one in the app directory
– nyxee
Oct 23, 2020 at 11:59

Add a comment |

Henadzi Rabkin · Accepted Answer · 2016-09-30 08:22:57Z

5

Root-gradle file:

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:x.x.x'
    }
}

allprojects {
    repositories {
        jcenter()
    }
}

Gradle-wrapper.properties file:

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-x.x-all.zip

edited Sep 30, 2016 at 8:22

answered Nov 25, 2014 at 14:42

Henadzi Rabkin

6,9533 gold badges33 silver badges40 bronze badges

Add a comment |

codersaif · Accepted Answer · 2020-05-06 19:25:38Z

4

In the project level build.gradle file, I have replaced this line

classpath 'com.android.tools.build:gradle:3.6.3'

with this one

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

After adding both of those lines, and syncing, everything became fine. Hope this will help someone.

answered May 6, 2020 at 19:25

codersaif

9569 silver badges16 bronze badges

Add a comment |

garnet · Accepted Answer · 2016-02-29 06:48:25Z

I am writing this not as a solution meant for many, but for some people who may commit a simple mistake like specifying the wrong url for importing projects from SVN. It is intended for those guys :)

This happened to me when I imported the project from SVN -> automatic prompt by Studio to open the project -> It asked for Gradle location -> D:\Software\Android\gradle-2.5 -> Then the error.

The same project in a different SVN branch works fine with the Gradle plugin and Gradle which I have configured in Studio. I tried changing Android Gradle plugin and Gradle to get it working on the erring branch without any success.

Finally, I figured out that it was my following mistake: I tried importing a specific Application alone instead of importing the application along with dependent library projects. The url which I used for import initially had the Application porject's name at the end. Once I removed it, and specified the parent directory which contained both application project and its dependent project, everything went smooth :)

David Rawson · Accepted Answer · 2017-06-12 05:48:08Z

3

I found the problem after one hour struggling with this error message:

I accidentally renamed the root build.gradle to filename in builde.gradle, so Android Studio didn't recognize it anymore.

Renaming it to build.gradle resolved the issue!

edited Jun 12, 2017 at 5:48

David Rawson

21k8 gold badges91 silver badges129 bronze badges

answered May 27, 2017 at 17:48

Lorenzo Barbagli

1,2512 gold badges16 silver badges34 bronze badges

Add a comment |

Simon Fakir · Accepted Answer · 2017-11-01 13:15:04Z

3

I still got the error

 Could not find com.android.tools.build:gradle:3.0.0.

Problem: jcenter() did not have the required libs

Solution: add google() as repo

buildscript {
    repositories {
        google()
        jcenter()

    }
    dependencies {

        classpath "com.android.tools.build:gradle:3.0.0"
    }
}

answered Nov 1, 2017 at 13:15

Simon Fakir

1,75219 silver badges21 bronze badges

Add a comment |

Volodymyr Kulyk · Accepted Answer · 2016-05-16 06:56:17Z

2

Go to your grade file where you can see this:

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:2.1.0'


        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

And change classpath to this:

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
//        classpath 'com.android.tools.build:gradle:2.1.0'
        classpath 'com.android.tools.build:gradle-experimental:0.7.0-alpha1'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

answered May 16, 2016 at 6:56

Volodymyr Kulyk

6,5153 gold badges37 silver badges64 bronze badges

No. gradle-experimental is "experimental". This has nothing to do with the question.
– Jared Burrows
May 22, 2016 at 14:09
@JaredBurrows The error in OP's question can happen with gradle-experimental as well. It is happening to me today. However, VladimirKulyk should know that using gradle-experimental is only recommended for NDK builds.
– IgorGanapolsky
Jul 28, 2016 at 21:35

Add a comment |

John Smith · Accepted Answer · 2014-11-07 11:58:01Z

1

I was using IntelliJ IDEA 13.1.5 and faced with the same problem after I changed versions of Picasso and Retrofit in dependencies in build.gradle file. I tried use many solutions, but without result. Then I cloned my project from remote git (where I pushed it before changing versions of dependencies) and it worked! After that I just closed current project and imported old project from Gradle file to IntelliJ IDEA again and it worked too! So, I think it was strange bug in intersection of IDEA, Gradle and Android plugin. I hope this information can be useful for IDEA-users or anyone else.

answered Nov 7, 2014 at 11:58

John Smith

6054 silver badges15 bronze badges

Is there a technical answer you can give with a specific code example?
– IgorGanapolsky
Jul 28, 2016 at 21:37

Add a comment |

Tom Chalker · Accepted Answer · 2016-12-27 16:05:16Z

1

Make sure your two build.gradle and settings.gradle files are in the correct directories as stated in https://developer.android.com/studio/build/index.html

Then open "as existing project" in Visual Studio

Gradle is very finicky about this.

answered Dec 27, 2016 at 16:05

Tom Chalker

111 bronze badge

Add a comment |

Dimitri Mestdagh · Accepted Answer · 2017-07-10 08:51:23Z

1

The other answers didn't work for me, I guess something wrong happens between ButterKnife and 3.0.0 alpha5.

However, I found that when I annotated any one sentence, either BUtterKnife or 3.0.0 alpha5, it works normally.

So, you should just avoid the duplication or conflict.

edited Jul 10, 2017 at 8:51

Dimitri Mestdagh

43.4k14 gold badges102 silver badges136 bronze badges

answered Jul 10, 2017 at 8:10

Lancer.Yan

86713 silver badges10 bronze badges

When I annotated any one sentence , either ButterKnife or 3.0.0 alpha5 , it works normally .
– Lancer.Yan
Jul 10, 2017 at 8:12
Please make a new question instead answering here with a question.
– ישו אוהב אותך
Jul 10, 2017 at 8:15
Remember that every alpha release is not ready for production. You mustn't use alpha version in your code.
– ישו אוהב אותך
Jul 10, 2017 at 8:16
Sorry... I solved this question on my computer , but I can't understand WHY ....
– Lancer.Yan
Jul 10, 2017 at 8:17
Maybe this unconventional method will helps . Annotated any one will helps in Android Studio 3.0.0 alpha5 .
– Lancer.Yan
Jul 10, 2017 at 8:19

| Show 4 more comments

Wouter Florijn · Accepted Answer · 2019-08-13 16:09:03Z

1

For future reference: For me, this issue was solely caused by the fact that I wasn't running Android Studio as administrator. I had the shortcut on Windows configured to always run as administrator, but after reinstalling Android Studio, the shortcut was replaced, and so it ran without administrator rights. This caused a lot of opaque errors, including the one in this question.

answered Aug 13, 2019 at 16:09

Wouter Florijn

2,8312 gold badges23 silver badges38 bronze badges

Add a comment |

Nathan Getachew · Accepted Answer · 2021-02-08 13:53:48Z

1

This issue happened when I accidently renamed the line

apply plugin: 'com.android.application'

on file app/build.gradle to some other name. So, I fixed it by changing it to what it was.

answered Feb 8, 2021 at 13:53

Nathan Getachew

7815 silver badges16 bronze badges

Add a comment |

A v o c a d o · Accepted Answer · 2021-03-09 12:24:41Z

1

[FOR FLUTTER] go to your build Gradle then check if you have three paths

dependencies {
    classpath 'com.android.tools.build:gradle:3.5.0'
    classpath 'com.google.gms:google-services:4.3.2'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
}

I somehow removed the android tools classpath and was getting the error.

answered Mar 9, 2021 at 12:24

A v o c a d o

5464 silver badges3 bronze badges

Add a comment |

Edison Spencer · Accepted Answer · 2015-09-08 22:15:09Z

0

This just happened to me using Android Studio 1.3.2, however, since I had just created the project, I deleted it and created it again.
It seems that it had not been properly created by Android Studio the first time, not even the project folders where as expected.

answered Sep 8, 2015 at 22:15

Edison Spencer

4931 gold badge9 silver badges24 bronze badges

Android Studio version should match the plugin version.
– Jared Burrows
Mar 9, 2016 at 1:59

Add a comment |

Victor Choy · Accepted Answer · 2016-04-12 06:00:12Z

0

If you run a the module task with android plugin 1.2.3 in module directory , the problem appears. Try this:

../gradlew -b ../build.gradle  -c ../settings.gradle  :module:xxx

answered Apr 12, 2016 at 6:00

Victor Choy

4,18828 silver badges37 bronze badges

1

This command is very hacky and Gradle 1.2.3 is extremely old.
– Jared Burrows
Apr 13, 2016 at 22:13

Add a comment |

David Rawson · Accepted Answer · 2017-06-12 09:34:47Z

I got this error message after making the following change in my top-level build.gradle to update to the latest version of gradle:

//classpath 'com.android.tools.build:gradle:2.3.2' old
classpath 'com.android.tools.build:gradle:2.3.3' //new

I foolishly made the change while I was connected behind a hostile workplace proxy. The proxy caused the .jar files for the new version of gradle to become corrupt. This can be verified by inspecting the jars to see if they are an unusual size or whether they can be unzipped.

In order to fix the mistake, I connected to my network at home (which is not behind a proxy) and did a refresh dependencies from the Terminal:

./gradlew --refresh-dependencies

This caused the newer version of gradle to be re-downloaded and the error no longer occurs.

Amir Dora. · Accepted Answer · 2018-08-09 11:51:57Z

0

Check the spelling, mine was 'com.android.aplication'

edited Aug 9, 2018 at 11:51

Amir Dora.

2,7964 gold badges42 silver badges65 bronze badges

answered Mar 13, 2018 at 21:52

k4dima

6,1395 gold badges42 silver badges40 bronze badges

Add a comment |

Igor · Accepted Answer · 2019-02-13 11:25:08Z

0

This may also happen when you have both settings.gradle and settings.gradle.kts files are present in project root directory (possibly with the same module included). You should only have one of these files.

answered Feb 13, 2019 at 11:25

Igor

2,08923 silver badges27 bronze badges

Correct. This happened to me when I imported my project directly with build.gradle, found duplicate Gradle and properties file
– Okikioluwa
Jan 3, 2020 at 1:03

Add a comment |

Madhavarao Kulkarni · Accepted Answer · 2021-03-04 08:41:22Z

0

i had similar problem and i did following things to resolve it. i referred to https://developer.android.com/studio/build and copy / pasted these following lines before apply plugin lines

repositories {
    google()
    jcenter()
}

dependencies {
    classpath 'com.android.tools.build:gradle:4.0.0'
}

}

answered Mar 4, 2021 at 8:41

Madhavarao Kulkarni

901 silver badge10 bronze badges

jcenter has been obsoleted now
– Raulp
May 18, 2023 at 10:59

Add a comment |

Mansuu.... · Accepted Answer · 2016-03-17 05:32:49Z

module app build.gradle file

apply plugin: 'com.android.application'

model{


    android {
        compileSdkVersion 23
        buildToolsVersion  "23.0.2"

        defaultConfig.with {
            applicationId "com.iamsafe"
            minSdkVersion 15
            targetSdkVersion 23





        }
     buildTypes {
            debug {
                minifyEnabled = false
                useProguard = true
                proguardFiles.add(file('proguard-rules.txt'))


            }
        }



    }

}



dependencies {
    compile 'com.android.support:support-v4:23.0.2'
    compile files('libs/asmack-android-8-0.8.10.jar')
    compile files('libs/commons-io-2.0.1.jar')
    compile files('libs/httpclient-osgi-4.2.1-sources.jar')
    compile files('libs/httpcore-4.3.2.jar')
    compile files('libs/httpmime-4.1.2.jar')
}


project build.gradle

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

allprojects {
    repositories {
        jcenter()
    }
}

David Rawson · Accepted Answer · 2017-06-12 06:03:51Z

In this case of issues check below code

dependencies {
    classpath 'com.android.tools.build:gradle:**1.5.0**'
}

and gradle-wrapper.properties inside your project directory check below disctributionUrl:

distributionUrl=https\://services.gradle.org/distributions/gradle-2.9-all.zip

If these are not compatible with each other then you end up in this issue.

For com.android.tools.build:gradle:1.5. you need a version at least 2.8 but if you switch to a higher version like com.android.tools.build:gradle:2.1.0 then you need to update your gradle to 2.9 and above this can be done by changing distributionUrl in gradle-wrapper.properties to 2.9 or higher as below

distributionUrl=https\://services.gradle.org/distributions/gradle-2.10-all.zip

Топчик · Accepted Answer · 2020-09-16 12:02:58Z

-1

If you work on Windows , you must start Android Studio name by Administrator. It solved my problem

answered Sep 16, 2020 at 12:02

Топчик

1299 bronze badges

Add a comment |

Diogo Miranda · Accepted Answer · 2017-12-21 15:21:00Z

-3

Just make sure you put the http and https proxy correctly when you create the app

answered Dec 21, 2017 at 15:21

Diogo Miranda

1

Add a comment |

Collectives™ on Stack Overflow

Error:(1, 0) Plugin with id 'com.android.application' not found

25 Answers 25

Updated Answer (Dec. 2, 2020)

Original Answer

It should look like this

Not the answer you're looking for? Browse other questions tagged
android
flutter
gradle
android-gradle-plugin
or ask your own question.

Linked

Hot Network Questions

Collectives™ on Stack Overflow

25 Answers 25

Updated Answer (Dec. 2, 2020)

Original Answer

It should look like this

Not the answer you're looking for? Browse other questions tagged androidfluttergradleandroid-gradle-plugin or ask your own question.

Linked

Related

Not the answer you're looking for? Browse other questions tagged
android
flutter
gradle
android-gradle-plugin
or ask your own question.