How to fix this error "A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade"

Question

I can't run my app on AVD. I get this error.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade

My build.gradle

android {
compileSdkVersion 29
buildToolsVersion "29.0.2"
defaultConfig {
    applicationId "com.example.myapplication"
    minSdkVersion 15
    targetSdkVersion 29
    versionCode 1
    versionName "1.0"
    testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
    }
}[E][1]}

dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'androidx.appcompat:appcompat:1.1.0'
implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
testImplementation 'junit:junit:4.12'
androidTestImplementation 'androidx.test:runner:1.2.0'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'}

https://stackoverflow.com/questions/57606462/a-failure-occurred-while-executing-com-android-build-gradle-internal-tasks — Sana Ebadi, Sep 24 '19 at 16:49
@sanaebadi I fixed 'org.gradle.jvmargs=-Xmx4608m' in gradle.properties but it's can't work. Still error at same. :( — Worramet Chairungruang, Sep 25 '19 at 11:02
@sanaebadi My build.gradle for project and gradle-wrapper are on my comment. — Worramet Chairungruang, Sep 25 '19 at 14:02
Does this answer your question? [A failure occurred while executing com.android.build.gradle.internal.tasks](https://stackoverflow.com/questions/57606462/a-failure-occurred-while-executing-com-android-build-gradle-internal-tasks) — VahidHoseini, Jan 14 '21 at 21:12
Recommend updating your gradle and gradle plugin as well as your compileSdkVersion (current is 31) and then bump build tools version to match that (should be 30.0.3 to match compileSdk 31). If you get a "corrupted build tools" error asking you to reinstall the tools ( i did when I first upgraded our project) please see the solution to the below question to fix the issue, you will need to change some file types under the Gralde files https://stackoverflow.com/questions/68387270/android-studio-error-installed-build-tools-revision-31-0-0-is-corrupted — Nicolas Mage, Feb 03 '22 at 21:45

score 34 · Answer 1 · edited Jun 30 '20 at 14:14

34

Finally I fixed it.

Change org.gradle.jvmargs=-Xmx1536m to org.gradle.jvmargs=-Xmx1536m -Duser.country=US -Duser.language=en
Change classpath 'com.android.tools.build:gradle:3.5.0' to classpath 'com.android.tools.build:gradle:3.4.2'

Android Studio - How to fix Internal error when trying to read zip file

edited Jun 30 '20 at 14:14

Boken

4,825
10
32
42

answered Sep 26 '19 at 08:31

Worramet Chairungruang

673
1
6
6

4

Thank you man, `org.gradle.jvmargs=-Xmx1536m -Duser.country=US -Duser.language=en` worked for me – LeoSantana Apr 16 '20 at 21:47
1

I change for my part `classpath 'com.android.tools.build:gradle:3.5.3'` to `classpath 'com.android.tools.build:gradle:3.5.2'` – gigeos Oct 03 '20 at 17:45

score 11 · Answer 2 · edited Jun 30 '20 at 14:13

11

Simply degrade the version from

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

to

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

then no need to change anything,

You can try Invalidate Caches/Restart if not working.

edited Jun 30 '20 at 14:13

Boken

4,825
10
32
42

answered May 17 '20 at 05:33

Sumit Singh

1,150
13
17

2

Had to downgrade from Gradle version 4.0.0 to 3.4.2 while building with Ionic. Do you by any chance know why this solution works? – EnigmaTech Oct 04 '20 at 18:48
2

Downgrading from 4.0.1 to 3.4.2 was the only solution that worked for me. Thanks! – YEG Oct 08 '20 at 21:45

score 3 · Answer 3 · edited Jun 30 '20 at 14:17

3

This worked:

gradle.properties.org.gradle.jvmargs=-xmx4608m

edited Jun 30 '20 at 14:17

Boken

4,825
10
32
42

answered Apr 10 '20 at 05:05

silexcorp

1,151
1
12
13

1

Earlier, invalidate cache and restart worked for me but the problem surfaced again. Then gradle.properties.org.gradle.jvmargs=-xmx4608m worked. – Sam Reyes Jul 13 '20 at 16:38

score 2 · Answer 4 · answered Apr 17 '20 at 12:03

Make sure you have enough RAM for gradle process by updating org.gradle.jvmargs in your gradle.properties.

Make sure your Gradle version and gradle plugin are compatible; refer to this table: https://developer.android.com/studio/releases/gradle-plugin#updating-gradle (i suggest plugin 3.5.3 with gradle 5.4.1 as of this writing!)

And what might be happening to some without knowing it, is not using JDK 8! I tried with JDK 11 and saw many different R8 and dexing errors! Also looks like this whole setup does not work with Eclipse OpenJ9 JDK distribution! so make sure you are using standard OpenJDK of your OS (mine would be default OpenJDK-8 from Debian)

I modified my `gradle.properties` file with the following line to solve OutOfMemroyError exception while running an Android build. My understanding is that this is double the default memory settings, and that increasing the Xmx value will give better results vs the XX:MaxPermSize parameter. If you need more, just increase the Xmx parameter. `org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m` — Tyler Forsythe, Sep 24 '21 at 19:59

score 2 · Answer 5 · answered Apr 26 '20 at 18:07

2

I had the same issue in my flutter project and it happened suddenly when trying to build/debug. Nothing worked not even "File > Invalidate Caches/Restart..." Finally I did a "flutter clean" and "flutter packages get" and it worked.

answered Apr 26 '20 at 18:07

PearlByte

59
3

score 2 · Answer 6 · answered Dec 26 '20 at 22:45

2

Run Flutter Clean, then restart your machine.

That did it for me.

answered Dec 26 '20 at 22:45

Robert

21
1

score 2 · Answer 7 · answered Mar 18 '21 at 17:03

2

For those who are scared of degrading gradle or so, recommend doing it because that resolved the issue for me. Dowgraded from:

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

to:

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

answered Mar 18 '21 at 17:03

SenyaOhar

81
1
8

score 1 · Answer 8 · answered Dec 25 '19 at 13:49

1

This error can also be arise due any vector asset. I resolve by removing that vector asset file. Please check if you recently made any change to your vector asset file.

answered Dec 25 '19 at 13:49

pankaj

29
1

score 1 · Answer 9 · edited Oct 08 '20 at 13:21

1

I'm using Android Studio 4.0.0 and everything is fine until suddenly I got this error when clean and rebuild project. I don't know why. I tried many solution suggested but no luck. Finally I try to uninstall Android Studio 4.0.1 and this error is GONE and enable to run in emulator like before

edited Oct 08 '20 at 13:21

Dharman

30,962
25
85
135

answered Jul 15 '20 at 04:43

Lahardi Alkawero

331
2
4

score 1 · Answer 10 · answered Aug 23 '20 at 12:11

Had same issue, proposed solutions did't work for me. In my case problem was caused by signing config: I did set storePassword field, but didn't set keyPassword field in my signingConfigs section (passwords were same). So if you have your signing config in app's build.gradle file, try to set Key Password field in File -> Project Structure -> Modules dialogue or by adding keyPassword field in your signingConfigs section in build.gradle:

android {
    signingConfigs {
        release {
            storeFile file('C:\\PathToKey\\key.jks')
            storePassword 'myPassword'
            keyAlias 'myAlias'
            keyPassword 'myPassword'
        }
    }
    ...
}

For some reason, the way I had it set up to pull the keyPassword from a file stopped working. I'd have NEVER thought to investigate that based on this extremely weird error, thanks so much! — kodi, Nov 03 '21 at 20:50

score 1 · Answer 11 · answered Sep 06 '20 at 12:44

1

It worked.Use these commands on VSCode.

flutter clean
flutter pub cache repair

answered Sep 06 '20 at 12:44

nafees ahmed

948
1
12
18

score 1 · Answer 12 · answered Nov 01 '20 at 14:36

In my case problem arose due to gradle version upgradation from 6.2 all to 6.6 all in gradle wrapper. So i wiped data of avd and restarted it and then deleted .gradle folder in android/.gradle and then run yarn start --reset-cache and yarn android. Then it worked for me

score 1 · Answer 13 · answered Jul 14 '21 at 01:00

1

Adding this line to gradle.properties.

org.gradle.jvmargs=-Xmx4608m

answered Jul 14 '21 at 01:00

Kingsley Mitchell

2,412
2
18
25

Can you give an explanation for why this worked for you? – Nicolas Mage Feb 03 '22 at 21:49

score 1 · Answer 14 · answered Jul 31 '21 at 07:39

I got the same error. This solved mine.

Change 'com.android.tools.build:gradle:3.5.0' to 'com.android.tools.build:gradle:4.1.3'
File -->> Invalid caches/Restart
pubspec.yaml -->> pub upgrade
Change dependencies version to latest
Pub get
flutter run

score 0 · Answer 15 · answered Apr 15 '20 at 15:54

0

Check if your APK is locked by external tool (or even IDE)

(...)\app\release\app-release.apk

answered Apr 15 '20 at 15:54

Grzesl

41
5

score 0 · Answer 16 · answered May 18 '20 at 02:34

0

In my case i was mentioned android:src = "@drawable/screen" in launch_background.xml file.

but, could not added image in drawable folder. Putting image screen.jpg in drawable folder fixed my issue.

answered May 18 '20 at 02:34

Avijit Nagare

8,482
7
39
68

1

This pointed me in the right direction, I had typo in my launch_screen.xml, thanks a lot! – effeKtSVK Jan 20 '22 at 14:38

score 0 · Answer 17 · answered May 06 '23 at 08:56

0

I had the same issue and I upgrade the compiled SDK version and IT worked fine.

answered May 06 '23 at 08:56

Liza

23
8

score 0 · Answer 18 · answered Jul 11 '23 at 16:59

0

For FLutter, make sure you added android/key.properties

storeFile=/Users/umerwaqas/Downloads/keystore/THREADS AI.jks
storePassword=123456
keyAlias=userapp
keyPassword=123456

answered Jul 11 '23 at 16:59

Umer Waqas - Top rated dev

3,072
29
26

score -1 · Answer 19 · answered Jul 01 '21 at 08:44

-1

In my case I solved the problem

uninstalling my antivirus which was fishy (downloaded from chrome).

"ionic cordova build android" command started working again

answered Jul 01 '21 at 08:44

Avkro

1

score -2 · Answer 20 · answered Sep 17 '21 at 15:27

-2

well the thing i do was simply restarting my computer. It works for a lot of these kind of rubbish errors android studio raises.

answered Sep 17 '21 at 15:27

alper yolcu

39
7

score -2 · Answer 21 · answered Jan 29 '22 at 07:56

-2

player - publishing setting- build under - custom main manifest deselect build again

answered Jan 29 '22 at 07:56

emrettc

1
1

score -3 · Answer 22 · answered Sep 25 '19 at 14:01

My build.gradle (Project)

buildscript {
repositories {
    google()
    jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:3.5.0'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}
}
allprojects {
repositories {
    google()
    jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}

My gradle-wrapper

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

How to fix this error "A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade"

22 Answers22

Linked