Develop Reference

Can't run nor debug project but gradle build+install work

After update to Android studio 3.6 Canary11 (macOS) I cannot run nor run Debug variants of my project (Release variants working fine).
When I try to run the project I've got error:
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> Entry name 'firebase-abt.properties' collided
But when I delete build directory (rm -rf app/build), I can run/debug project once time. After the first run, it is again with the same error with collision.
I try clear cache, restart the Android studio, but it didn't help.
Maybe it is not related to Android studio, because different project running ok.
Do you have any idea, what the problem may be?

I was facing the same error as MrEngineer13. After hours of struggle turns out you have to delete the built APK files for the project to build another APK successfully

I had a similar issue with Android Studio 3.6 Canary 12 on Mac, I could build different build variants but had this error when I tried to Generate a signed apk:
Entry name 'kotlin/collections/MapWithDefault.kotlin_metadata' collided
I had to delete the .build folder as well as the folders where I build my build variant.

I faced somehow similar issue on Android Studio 3.6.3v
Entry name 'kotlin/collections/MapWithDefault.kotlin_metadata' collided
I resolved the issue by:
Delete build folder under /app
Clean project
Rebuild project
If still doesn't work, do the following:
File > Invalidate Caches/Restart

I just had a similar issue - my generating a debug build variant kept failing with an error about "Entry name res/layout/test_toolbar.xml collided". There is no "test_toolbar_xml" anywhere in my project. I first deleted all build directories and tried - same result. then I went in and deleted caches under .gradle\5.6.4, and under .idea folders. Tried again and this time I was able to build.
Building a "release" variant worked every time.

Delete apk file from subfolders project

try build.gradle
android {
packagingOptions {
pickFirst 'firebase-abt.properties'
}
}

If anyone is still facing this issue, try this -
Step 1
File > Invalidate Caches/Restart
Step 2
Rebuild Project

This is caused by the Android studio's new default packaging tool called zipflinger
You have to set the following in your gradle.properties file to fix the issue.
android.useNewApkCreator=false
Reference: https://developer.android.com/studio/releases/gradle-plugin?authuser=1#zipflinger

After upgrading Gradle, compilation (debug) failed. I got the compilation error message:
Entry name 'res/mipmap-hdpi-v4/ic_launcher.png' collided
Tried the article https://medium.com/#elye.project/resources-collision-without-warning-b29294f518c6 by Elye.
I am using a library where ic_launcher is also defined. I renamed the ic_launcher according to recommendations in the article, but that did not solve the problem.
Tried to clear the cache by deleting the build and gradle directory, but that did not solve the problem.
Tried to set in gradle.properties:android.useNewApkCreator=false but then Android Studio reports:
build.gradle: The option setting android.useNewApkCreator=false is experimental and unsupported.
Since I am not up to using experimental features, I downgraded from:
Gradle Version: 3.6.1
Android Plugin version: 6.2.1
to:
Gradle Version: 3.5.3
Android Plugin version: 5.4.1
Compilation (debug) now works again.

I faced the same problem. I just clean and rebuild, and it's working fine after that.

When getting a entry name 'kotlin/collections/mapwithdefault.kotlin_metadata' collided error in Android Studio v3.6.1 it helped cleaning the build folders.
We ended up creating a script for this: cleanBuldFolders.sh
#!/bin/bash
# Deletes all build folders in the project
find . -name build -type d -exec rm -rf {} +

I faced the same issue when using Android Studio 4.0 Canary 8.
I solved my problem by downgrading from:
Gradle version 3.6.3 to 3.5.3
Android plugin version 5.6.1 to 5.4.1
BUT
I would suggest try these below options before downgrading
Delete build folder inside app
Clean
Rebuild
If you still face the issue, try Invalidate Cache / Restart

How to fix 'Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: No outputs for the main artifact of variant:'

I am trying to run a selected build variant but giving me following error in Run tab,
Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: No outputs for the main artifact of variant: madhyapradesh-debug
So kindly suggest the solution to it.

First clean your project by
Build -> Clean project
Then rebuild project
Build -> Rebuild project
Then run your project.
I hope this will work.
if not then go to
File -> Invalidate Caches / Restart -> Invalidate and restart
The last option is you can sync Gradle again in case nothing worked

Your Gradle is out of sync. Go to: File -> Sync Project with Gradle Files. It should fix the problem.

This is because your gradle version in project build.gradle configuration is too old for a newer Android Studio version, like Android Studio 3.6.1,
1. you should change the gradle configuration into a newer one under:
build.gradle(project)->buildscript->dependencies->classpath;
for example, you should change:
classpath 'com.android.tools.build:gradle:2.3.1'
into:
classpath 'com.android.tools.build:gradle:3.1.2'
2. after this, may be you should also change the configuration in gradle-wrapper.properties into a newer version, for example, change:
distributionUrl=https\://services.gradle.org/distributions/gradle-3.3-all.zip
into:
distributionUrl=https\://services.gradle.org/distributions/gradle-4.4-all.zip
3. after this, may be you should also add google() at:
build.gradle(project)->buildscript->repositories
and
build.gradle(project)->allprojects->repositories

I have the same issue with a Cordova Project after I updated Android Studio to 3.6.1
As a workaround (at least for the first installation of the app) I use installDebug Gradle Task from Gradle Tab View -> Tasks -> Install

I faced this problem today.
Select nothing from the installation option and click on the add icon button. Select Run Gradle task.
Double click on the run Gradle task and there will be a pop-up option like the image. Change the first option to the app and the second option to install debug like the image.
Now finally you solved the problem

For me doing:
File -> Invalidate Caches / Restart
worked fine ^^

For me the solution was apparently to update the Gradle plugin...

Workaround 1
Create a new configuration for Run with the same parameters as the default config app. This work for me.
Run
Edit Configuration
Add New Configuration (NOT COPY) -> Android App
Rename
Choose app Module
Apply
Workaround 2
Use the task for install in Gradle Tab View -> Tasks -> Install
Run the app.
Workaround 3
Delete .gradle folder
Invalidate Caches / Restart ...
Run the app

I faced this problem today.
Select "Default APK" from the installation option and click on the add icon button. Select "Gradle-aware Make"->"OK"

Sometimes a gradle sync and run will do the job. I was facing this after gradle plugin update too. Gradle sync might not have happened sometimes.

Do follow the three steps:
Clean project: Build(menu) >> Clean Project
Sync project: File(Menu) >> Sync Project with Gradle Files
Rebuild project: Build(menu) >> Rebuild Project
Now run your app and enjoy.

First clean your project and then rebuild the project it will solve the problem

Set Deploy to NOTHING worked for me. (kudos to above nvatvm above)

Ensure that your have set applicationId "com.example.myapp" in your build.gradle
android {
...
defaultConfig {
applicationId "com.example.myapp"
minSdkVersion 19
targetSdkVersion 28
versionCode 1
versionName "1.0"
}
...
}
And from app -> Edit Configurations, ensure that you have selected "Default Activity"

Project Structure -
Suggestions -
Update Gradle

First of all Clean Project and Rebuild Project. If it doesn't work then the Easy, Hardcore, Fast approach which works for me was just deleting the two following folder named .gradle and .idea after closing the IDE and restart it -

Try running the following command on the Android Studio Terminal:
gradlew connectedAndroidTest

My solution was to upgrade Android Studio from "Artic Fox | 2021.3.1 Canary 12" to "Artic Fox | 2021.3.1 Canary 13"

You need to update the Gradle version:
go to File -> Project structure, then update the Android Gradle Plugin version, and Gradle Version to the latest stable versions(now 7.0.2 & 7.2 respectively)

The other answers are not working for me.
The only solution that worked for me was to delete .gradle and .idea folders.

View Gradle Table => right click the application => click "Reload Gradle Project"

Check if you have Build Variant selected:
Go to Menu > Build > Select Build Variant
Select a build variant that ends with Debug for the Release Variants you need the signing certificate configured correctly.

setting Installation Options-> Deploy: APK from app bundle worked for me.

Nothing worked for me like the clean build, rebuild and invalidate cache restart.
Here's my solution to this problem.
The workaround was to delete the existing app configuration from Run/Debug Configurations.
After that add new configuration by clicking the left top + icon and then add Android App.

The answer by #applixy worked for me.
1.Just note to update the classpath to the latest version
in project->build.gradle to
classpath 'com.android.tools.build:gradle:4.1.1'
2.And in the gradle->wrapper.proprties just apply sync with gradle upon
distributionUrl=https://services.gradle.org/distributions/gradle-6.5-all.zip
3.My project already had the google() method on allprojects{}.
So build your project and run you are good to go.

Error:
Unable to determine application id: com.android.tools.idea.run.ApkProvisionException: No outputs for the main artifact of variant: debug
Solution :
Go to:
File
project structure (Ctrl + Alt + Shift + S)
Suggestions
Update Graddle
Then wait for downloading griddle to solve your problem.

Build error in android studio after updating to stable Android studio 3.1.2

I was trying to build an application. I was successful in making project(ctrl+F9) after that I tried to run my application on the emulator in this process I got the build error. To fix this issue I got a suggestion from Android studio to change build script to following:
To proceed, either fix the issues identified by lint or modify your build script as follows:
android {
lintOptions {
checkReleaseBuilds false
// Or, if you prefer, you can continue to check for errors in release
//builds,
// but continue the build even when errors are found:
abortOnError false
}
}
Where could I find the build script? So, that I can change it. I am a newbie to the Android world.

The build script can be found in the Gradle Scripts option in the very left of the screen.
Click the Gradle scripts to display all the gradle files and there you will find
These two files marked with red color are the build.gradle files for your project.

try to clean your project, then build it again. if the result still the same, try to invalidates cache & restart.

Go to android studio then File -> Invalidate Caches / Restart...

Android Studio build fails with "Task '' not found in root project 'MyProject'."

I get this error when trying to build my project after changing laptop and updating to Android Studio version 0.8.2.
FAILURE: Build failed with an exception.
What went wrong:
Task '' not found in root project 'MyProject'.
Try:
Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Here are my Gradle files:
Top Level settings.gradle
include ':MyProject'
build.gradle in MyProject:
apply plugin: 'com.android.application'
buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath "com.android.tools.build:gradle:0.12.+"
}
}
repositories {
mavenCentral()
}
android {
compileSdkVersion 20
buildToolsVersion "20"
defaultConfig {
minSdkVersion 14
targetSdkVersion 20
}
}
dependencies {
compile 'de.timroes.android:EnhancedListView:0.3.0#aar'
compile 'com.nineoldandroids:library:2.4.0'
}
Top level build.gradle is empty

Though late in answering, this is a hard one to Google (the single quotes) and it’s not clear what’s happening. I don't have the reputation yet to comment or ask for scope (or post 3 links), so this answer may be a little tedious.
To answer fast, you may have multiple Gradle plugins in your project.
Synchronize Gradle Wrapper and Plugins
My issue seemed to start with a corrupted IML file. Android Studio (between closing and reopening a project) began complaining an IML was gone (it wasn’t) and a module should be deleted, which I declined. It persisted, I upgraded to AS 0.8.7 (canary channel) and got stuck on the OP issue (Task '' not found in root project). This completely blocked builds so I had to dig in to Gradle.
My repair steps on OSX (please adjust for Windows):
Upgrade Android Studio to 0.8.7
Preferences | Updates | Switch "Beta Channel" to "Canary Channel", then do a Check Now.
You might be able to skip this.
Checked the Gradle wrapper (currently 1.12.2; don’t try to use 2.0 at this time).
Assuming you don’t need a particular version, use the latest supported distribution
$ vi ~/project/gradle-wrapper.properties ... distributionUrl=http\://services.gradle.org/distributions/gradle-1.12-all.zip
This can be set in Android Studio at Preferences | Gradle (but 0.8.7 was giving me ‘invalid location’ errors).
The 'wrapper' is just a copy of Gradle for each Android Studio project. It allows you to have Gradle 2 in your OS, and different versions in your projects. The Android Developer docs explain that here.
Then adjust your build.gradle files for the plugin. The Gradle plugin version must be compatible with the distribution/wrapper version, for the whole project. As the Tools documentation (tools.android.com/tech-docs/new-build-system/user-guide#TOC-Requirements) is slightly out of date, you can set the plugin version too low (like 0.8.0) and Android Studio will throw an error with the acceptable range for the wrapper.
Example, in build.gradle, you have this plugin:
dependencies {
classpath "com.android.tools.build:gradle:0.12.+"
}
You can try switching it to the exact version, like this:
dependencies {
classpath "com.android.tools.build:gradle:0.12.2"
}
and (after recording what version you’re changing from in each case) verifying that every build.gradle file in your project pulls in the same plugin version. Keeping the “+” should work (for 0.12.0, 0.12.1, 0.12.2, etc), but my build succeeded when I updated Google’s Volley library (originally gradle:0.8.+) and my main project (originally 0.12.+) to the fixed version: gradle:0.12.2.
Other checks
Ensure you don’t have two Android Application modules in the same Project
This may interact with the final solution (different Gradle versions, above), and cause
UNEXPECTED TOP-LEVEL EXCEPTION: com.android.dex.DexException: Multiple dex files define (various classes)
To check, Build | Make Project should not pop up a window asking what application you want to make.
Invalidate your caches
File | Invalidate Caches / Restart (stackoverflow.com/a/19223269/513413)
If step 2 doesn't work, delete ~/.gradle/ (www.wuttech.com/index.php/tag/groovy-lang-closure/)
Quit Android Studio
$ rm -rf ~/.gradle/
Start Android Studio, then sync:
Tools | Android | Sync Project with Gradle Files
Repeat this entire sequence (quit...sync) a few times before giving up.
Clean the project
Build | Clean Project
Project structure mismatch; see https://stackoverflow.com/a/64962359/8740349 for details.
If You See This...
In my recent builds, I kept seeing horrible fails (pages of exceptions) but within seconds the messages would clear, build succeeded and the app deployed. Since I could never explain it and the app worked, I never noticed that I had two Gradle plugins in my project. So I think the Gradle plugins fought each other; one crashed, the other lost its state and reported the error.
If you have time, the 1-hour video "A Gentle Introduction to Gradle" (www.youtube.com/watch?v=OFUEb7pLLXw) really helped me approach the Gradle build files, tasks, build decisions, etc.
Disclaimer
I'm learning this entire stack, on a foreign OS, after working a different career...all at the same time and under pressure. In the last few months I have hit every wall I think Android has; I've been here quite often and this is my first post. I thought this was a hard fix, so I sincerely apologize if the quality of my answer reflects the difficulty I had in getting to it.

Download system image(of targeted android level of your project) from sdk manager for the project you have imported.
This error comes when you do not have target sdk of your android project installed in sdk folder
for eg. Your imported project's target sdk level may be android-19 and on sdk folder->system-images you may have android-21 installed. so you have to download android-19 system image and other files from sdk manager or you can copy paste it if you have the system image.

Remove:
<facet type="android" name="Android">
<configuration />
</facet>
in your iml file. That works for me.
https://plus.google.com/+AlexRuiz/posts/49hP3V9GSGe

This happened to me recently when I close one Android Studio project and imported another Eclipse project. It seemed to be some bug in Android Studio where it preserves some gradle settings from previously open project and then get confused in the new project.
The solution was extremely simple: Close the project and shut down Android Studio completely, before re-opening it and then import/open the new project. Everything goes smoothly from then on.

Apparently this error has multiple causes. Here's what fixed it for me.
I was running the build command like this:
./gradlew :testapp: build
Running it without the space fixed the issue:
./gradlew :testapp:build

I got this error when switching from one Git branch to another, and then trying to run "Clean Project". I used ack to search for the Task name, and found it in a .iml file.
My solution was to regenerate the project's .iml file by clicking (in the main menu) Tools > Android > Sync Project with Gradle Files. (Thanks to this answer.)

In my case, setting the 'Gradle version' same as the 'Android Plugin version' under File->Project Structure->Project fixed the issue for me.

Simple fix for me was
Build > Clean project
Restart Android Studio

Yet another solution to the same problem:
This happened to me every time I imported an eclipse project into studio using the wizard (studio version 1.3.2).
What I found, quite by chance, was that quitting out of Android studio and then restarting studio again made the problem go away.
Frustrating, but hope this helps someone...

Sometimes, if you have opened two windows of Android Studio, and when you try to compile, this issue might happen. For me, when I was compiling a backed Google Cloud Endpoint module which was not embedded in a project, rather shared among different Android Studio projects, and when there is more than once instance open, this error use to spring up for me. But as soon as you close other windows, everything will be fine. Sometimes, you might have to restart Android Studio altogether.

I got this problem because it could not find the Android SDK path. I was missing a local.properties file with it or an ANDROID_HOME environment variable with it.

Make sure you have the latest values in your gradle files. As of this writing:
buildToolsVersion "21.1.2"
dependencies {
classpath 'com.android.tools.build:gradle:1.1.0'
}

Open Command Prompt
then go your project folder thru Command prompt
Type gradlew build and run

Apparently this issue caused by Android Studio on the various situation but the reason is build error When importing an existing project into android studio. In my case, I've imported my exist project where I was supposed to install few build tools then finally build configuration was done with error. In this case, just do the following things
Close the current project
File>New>Import Project (Don't use the open recent project)
Note:
I'm sure this kind of error is not on source code when this happened on Import project.

Problem
I specifically got the "[module_name]:prepareDebugUnitTestDependencies" task not found error, every time I ran gradle build. This happened to me after updating my Android Studio to 3.0.0.
Investigation
I had previously added command-line options to the gradle-based compiler, which you can find under: File -> Settings -> Build, Execution, Deployment -> Compiler -> Command-line Options. Specifically, I had excluded a number of tasks, including the aforementioned task. While that worked fine on the previous stable version (2.3 at that time), it seems like this was the reason behind the build failure.
Solution
This is one of many possible solutions.
Make sure you have the correct command-line options specified in the settings under: File -> Settings -> Build, Execution, Deployment -> Compiler -> Command-line Options, and that none of them is causing this problem.
In my case, I removed the exclusion of this task (and other tasks that seemed related), left the unrelated tasks excluded, and it worked!

I had the same problem and the "Tasks" tab doesn't appear to me on the Gradle settings, neither doing the commands gradlew signinReport or something.
I fix it doing the following steps:
1.- Add android: exported = "true" in my main activity of the AndroidManifest (because that Activity has an intent-filter)
2.- Update in Build.gradle (app) the compileSdkVersion to 31
3.- Update in the same place the targetSdkVersion also to 31.
4.- Click on "Sync now".
And that works for me.
Farewell!

For this you may simply just goto: SETTINGS > EXPERIMENTAL > Then uncheck the option:
"Do not build Gradle Task List during Gradle sync", Click on "Apply" > "Ok" and then click on the "Sync Project with Gradle files" option from the right side of the menu bar.
Your issue should be resolved.

Set the path of the root folder and after run the below command
ex : cd C:\Users\maha\Documents\gradle\gs-gradle-master\initial

This is what I did
Remove .idea folder
$ mv .idea .idea.bak
Import the project again

I remove/Rename .gradle folder in c:\users\Myuser\.gradle and restart Android Studio and worked for me

In my case, I meet this problem that compile options in Android Studio is "stacktrace." Modify stacktrace to --stacktrace, the problem solved.

I have solved this problem You just need to Create file in Android Folder
Go android folder
Create file local.properties
then just add this code in local.properties file:-
If you are using MacBook then sdk.dir=/Users/USERNAME/Library/android/sdk
if you are using Windows then sdk.dir=C:\Users\USERNAME\AppData\Local\Android\sdk
if you are using Linux then sdk.dir = /home/USERNAME/Android/sdk
if you want to know what is your system USERNAME then just use command for Mac whoami
and then just rerun command react-native run-android
Thanks :)

Am on Mac so answer is as per like that.
Go to Android Studio(From Menu Bar) -> Preferences -> Build, Execution, Deployment -> Compiler . Then look for Command-Line Options , there make sure nothing typed in its Text Field. That should be empty. Then rebulid project and thats it.

Gradle error: could not execute build using gradle distribution

After I updated Android Studio to version 0.2.7, I got the following error:
org.gradle.tooling.GradleConnectionException: Could not execute build
using Gradle distribution
'http://services.gradle.org/distributions/gradle-1.6-bin.zip'.: Could
not execute build using Gradle distribution
'http://services.gradle.org/distributions/gradle-1.6-bin.zip'.
This is my build.gradle:
buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath 'com.android.tools.build:gradle:0.5.+'
}
}
apply plugin: 'android'
dependencies {
compile files('libs/android-support-v4.jar')
}
android {
compileSdkVersion 17
buildToolsVersion "17.0.0"
defaultConfig {
minSdkVersion 10
targetSdkVersion 17
}
}
Does anyone know this error?

I had the same issue, can't say I know what caused it, but I just closed Android Studio, renamed the c:\users\MY USERNAME\.gradle directory to old-.gradle and then re-launched Android Studio.
Android studio then re-created the directory and automatically downloaded the gradle zip file and set it all up.
Seems to all be fine but to be honest I don't know what this directory is nor what the root cause of the problem was either, so proceed with caution and keep the old .gradle folder around for a bit until you're happy all is working fine.

For me the following two steps fixed the issue:
Make sure the Gradle build was successful
Android Studio - File - Invalidate Caches / Restart...

I suddenly had this issue in the morning after it working the night before. I tried all solutions here and failed.
I also tried installing another version of Gradle 1.8 and setting the gradle_home.
Tried restarting studio.
Eventually the tried and trusted method of restarting Windows worked for me.
All in all a frustrating waste of time.

I updated to 0.3.0 and had the same issue. I had to end up changing my Gradle version to classpath 'com.android.tools.build:gradle:0.6.1+' and in build.gradle and also changing the distributionUrl to distributionUrl=http\://services.gradle.org/distributions/gradle-1.8-bin.zip in the gradle-wrapper.properties file. Then I did a local import of the Gradle file. That worked for me.

I had this issue as well and jaywhy13 answer was good but not enough.
I had to change a setting: Settings -> Gradle -> MyProject
There you need to check the "auto import" and select "use customizable gradle wrapper". After that it should refresh gradle and you can build again. If not try a reboot of Android Studio.

First of all, JDK environment variable settings :
e.g) JAVA_HOME -> C:\develop\java\jdk\jdk1.8.0_25
path -> %JAVA_HOME%\bin;
eclipse
Window -> preferences -> Gradle -> Arguments -> Worksapce JRE check -> jdk(jdk1.8.0_25) choice
again Run -> gradle build :)

1- delete .gradle folder in the root directory of the app
2- invalidate cache and restart

As per answer by WarrenFaith, go to:
Settings -> Gradle -> Project-level settings
Change to Use customizable gradle wrapper.
Click OK and watch it build. If you still get an error at that stage, go back to:
Settings -> Gradle -> Project-level settings
Change it back to Use default gradle wrapper (recommended)
Click OK. That fixed it for me.

I had the same issue and i solved it by deleteing gradle-wrapper.jar and gradle-wrapper.properties file of Gradle wrapper then clean rebuild work for me.

I entered:
[C:\Users\user\].gradle\caches\1.8\scripts directory and deleted its content.
I didn't had to restart anything, just removed scripts content any rerun it.

For me, when using IntelliJ IDEA, this error arose because I had the Java SDK, rather than an Android SDK, set at the Project level.
My fix:
IntelliJ > File > Project Structure ...
Project > Project SDK > [Select] 'Android API 19 Platform (java version "1.7.0_40")'
I'm on:
IntelliJ IDEA: 13.1.3
Gradle: 1.10
Android Plugin for Gradle: 0.9.+

I had the same problem on Ubuntu with Eclipse 4.3 (Kepler) and the problem was that I created the project with a minus-sign in it.
I recreated the project with no specialchars and it all worked fine

I had the same Gradle build problems in Eclipse and by doing the following steps, the problems were solved:
set up project to use correct java version of java
project properties-> java build path -> jre system (edit the current one, and add the correct java jdk or jre there)
window->Preferences ->Gradle->Arguments-> Workspace JRE (set to the correct one)
Hope this will help those who have the same problems.

This happened to me after a java update, few things to check if you are sure your path has been set before:
if the path doesn't match the latest java install folder, change it (if your in eclipse check the eclipse.ini too to make sure your using your systems default vm (ie no VM tag) )
go to the java directory, there should be a 'jdk' and a 'jre' in the path, for example:
C:\Program Files (x86)\Java\jdk1.8.0_72\jre
if not you probably installed the JRE only not the JDK that
finally if the lib folder of the jdk (not jre) doesnt contain tools.jar then you have a problem with the install

I had a similar problem after doing brew install gradle. Perhaps it was because it was an older version. So I uninstalled and instead followed the gradle website's install instructions and then when I did gradle eclipse I no longer had the could not execute build using gradle distribution error.

This problem occurred to me when I edited the configurations in Android Studio to use the Desktop. However, using the default(android) seems to work well without any issues.

To correct this mistake very easily,
If you read logs. The problem occurs because of the sudden shutdown of the IDEA. And the log files do not correctly write data. Just delete the file on the path
C:/Users/{UserName}/.Gradle/demon/{gradleVersion}/registry.bin.lock.