Ошибка apply plugin com android application

I am working on an app. In my app there is no error in code but when I try to run my project it gives following errors.

Error:(1, 1) A problem occurred evaluating project ‘:app’.

Failed to apply plugin [id ‘com.android.application’]

Could not create plugin of type ‘AppPlugin’.

I try this also Gradle is issuing an error «Could not create plugin of type ‘AppPlugin'»

and this also Gradle errors in Android Studio

Following is my build.gradle file

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

android {

    compileSdkVersion 23
    buildToolsVersion "21.1.2"

    defaultConfig {
        applicationId "com.praval.healthfreak"
        minSdkVersion 15
        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.2.1'
    compile 'com.google.android.gms:play-services:8.3.0'
    compile 'de.hdodenhof:circleimageview:1.3.0'
    compile 'com.android.support:design:23.2.1'
    compile files('libs/YouTubeAndroidPlayerApi.jar')

}

Delete gradle cache files.
It can be in path like
C:Usersusername.gradlecaches
for Windows users.
For UNIX based operating systems it will be
~/.gradle/caches.

Just go to the gradle.properties file and change enableUnitTestBinaryResources from true to false

android.enableUnitTestBinaryResources=false

i fixed it by upgrade to gradle-5.6.4-all.zip in projectgradlewrappergradle-wrapper.properties

#Wed Mar 11 15:20:29 WAT 2020
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https://services.gradle.org/distributions/gradle-5.6.4-all.zip

answered Mar 11, 2020 at 14:56

answered Apr 24, 2022 at 22:28

On Mac Just Goto :

Android Studio -> Preference -> Gradle -> Gradle JDK -> Download JDK -> Ok

As in Accepted post, the problem solved with updating gradle to 4.4.1.

1. Get Latest Gradle 4.4.1 from here
2. Extract and put it in «C:Program FilesAndroidAndroid Studiogradle»
3. Then from android studio go to
   «File -> Settings -> Build, Excecution, Deployment -> Gradle», from Project-level settings: Select Use local gradle Distribution and give the above
   address(folder with name «gradle-4.4.1» in «C:Program Files …»)
4. Then make project.

My Problem solved this way.

answered Feb 27, 2018 at 9:36

In my case, if your version of build tools in the build.gradle file in the root folder like :

classpath ‘com.android.tools.build:gradle:3.x.x’ <— version of tools

is not supported by the Gradle installed in your project, you can check the build tools/plugin supported versions here, and make sure that the version installed in your project is supported by that version of Gradle.

You don’t need to upgrade Gradle, you just check if it supports the plugin installed in your project or not.

answered May 4, 2020 at 2:32

First update the gradle to the latest version, if the issue still persists (in my case it did) then do the below-
go to gradle.properties file and comment the line
android.enableUnitTestBinaryResources=true

click on sync now.

it should solve the issue.

answered Apr 12, 2021 at 18:28

answered May 9, 2021 at 15:01

answered Mar 10, 2020 at 9:25

Whenever you update your Gradle files do not forget to check the compatible Gradle wrapper distibutionUrl, in your case it happened because of the same.

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

answered Apr 22, 2020 at 7:01

Inside my project there is a .gradle folder which had cached the previous gradle version I was using (5.4.1) and gradle kept using that instead of my newly downloaded one (5.6.4).

Simply:

1. Close Android Studio
2. Delete the older gradle version folders from your project.
3. Restart Android Studio. Everything should be working correctly

In case this didn’t work you can also try the following:

• Delete all versions in project .gradle folder so only the new one is redownloaded by AS when reopening the IDE.
• Check your project settings for gradle build version and make sure it is set to the latest one.
• Check that other modules aren’t using older versions of the gradle build. You can search for this using project search (Ctrl+Shift+F) for "distributionUrl" and making sure that all modules have the latest version.
• Delete .gradle/caches under your root gradle folder, usually C://Users/{you}/.gradle
• try gradle build --stacktrace, --info, --scan or --debug in your AS terminal to get help and more info to debug your problem.

answered Jun 4, 2020 at 9:08

answered Mar 22, 2021 at 10:02

One of the causes of the following error could be that exists an incompatibility with the configured version of the JVM in the project regarding the JDK location.

Error:

org.gradle.api.plugins.InvalidPluginException: An exception occurred applying plugin request [id: 'com.android.application']

Caused by: java.lang.NoSuchMethodException: java.lang.invoke.MethodHandles.privateLookupIn(java.lang.Class, java.lang.invoke.MethodHandles$Lookup)
Caused by: java.util.concurrent.ExecutionException: java.lang.NoSuchMethodException: java.lang.invoke.MethodHandles.privateLookupIn(java.lang.Class, java.lang.invoke.MethodHandles$Lookup)
Caused by: java.lang.NoSuchMethodException: java.lang.invoke.MethodHandles.privateLookupIn(java.lang.Class, java.lang.invoke.MethodHandles$Lookup)

Workaround:

Note: For JVM version in compileOptions{} and kotlinOptions{}

• For JVM version: JavaVersion.VERSION_1_8
• Use JDK Location: /java-1.8.0-openjdk-amd64

• For JVM version: JavaVersion.VERSION_11
• Use JDK Location: /java-1.11.0-openjdk-amd64

I am facing same issue.
But I am able to run app from Android Studio

1. First, in a terminal/command-prompt, open Metro-Bundler, by running command:
   npm start from project folder (Ex: D:AwesomeProject>npm start)
2. Then in Android Studio, open ~/ProjectFolder/android (Ex: D:AwesomeProjectandroid), and click Play icon (or press Shift+F10 for windows).

Note: This worked on Emulator only.

answered Apr 9, 2022 at 19:02

This answer is only valid if you cloned your project. For example. I had an app for USA only and wanted to clone it for other countries. I copied the project then renamed each project folder with country name. The names were already in excel so using copy-paste some projects gave me this error. When I sorted by name, I noticed the problematic ones were not in the correct alphabetical position.

So if this happened to you after cloning or renaming an existing project folder in file explorer (especially if you made names in excel and copy pasted) it introduces non-ascii characters.

1. Close android studio
2. Navigate to project location (in my case D://published apps/project name)
3. right click and rename the project name without using paste, instead type it.
4. When you open android studio again it should work, otherwise follow the other answers above.

TIP: It helps if you have multiple folders as you can sort by name and see project names that do not adhere to alphabetical order.

answered Jul 20, 2022 at 10:36

Hello,
I am Dipak, I faced this issue because I have downloaded and built a project on my PC, and it is on old java version 1.8, so when project building it will ask me to change the java version, and I have accepted that.

Here is the Solution,
As you see my project need a java 11 version to build Gradle so,

1. GoTo File -> Settings
2. Build,Execution and Deployment -> Build Tools -> Gradle
3. Change java version, Apply and click Ok.
4. Sync build.gradle and run the project.

First of all, before trying the most complicated things you should make the step easier, in my case this bug just happened on my way until the project contained ‘spaces’ for example:

Replace:

C://Users/Silva Neto/OneDrive/Work space/project

With:

C://Users/SilvaNeto/OneDrive/Workspace/project

Notice that we replaced spaces with camelCase but you can choose any naming scheme you like, and hopefully this could solve your issue.

I hope this will help.