Android Studio error "Installed Build Tools revision 31.0.0 is corrupted"

Question

I'm on Android Studio 4.2.2. I created a new project and haven't added anything to the starter code and whenever I click build or run, I get this error:

Installed Build Tools revision 31.0.0 is corrupted. Remove and install again using the SDK Manager.

I've looked at other posts' suggestions, but neither of those solutions worked. Here's what I've tried:

SDK Manager → SDK Tools → check "Show package details", uncheck 31.0.0, and click "Apply" → Uninstall 31.0.0 → check 31.0.0 and reinstall it
In SDK Manager, deselect 31.0.0 and try installing an older version (e.g., I've tried 30.0.3) and update "buildToolsVersion" in build.gradle to the installed version
Went to Project Structure → Properties and verified that 31.0.0 is selected for "Build Tools Version" and "Compiled SDK Version"
Manually remove the stuff in the build-tools folder; i.e., rm -rf /path/to/android/sdk/build-tools/31.0.0 (it doesn't end in "-rc" like some other posts have described)
Restart Android Studio
Reinstall Android Studio

I'm an Android noob just trying to set up a hello world project, and it really shouldn't be this hard.

I would add to this that I can't seem to downgrade to Build Tools 30.0 which would be my go-to solution to an issue like this. — Kevin McCarpenter, Jul 15 '21 at 03:17
Figured it out, uncheck "Show Package Details" and then you can select a lower version. If you're not building for android 12 (and you probably aren't yet), you can uncheck "31.0.0" and check "30.0.3". After that, go into the build.gradle in your app and change `buildToolsVersion "31.0.0"` to `buildToolsVersion "30.0.3"` — Kevin McCarpenter, Jul 15 '21 at 03:21
that is weird because I did a fresh installation of android studio and got the same problem — gzinho, Jul 16 '21 at 23:27
this might be an issue with 31.0.0, wait for another update by Google! — Paramjit Singh Rana, Jul 19 '21 at 04:16
Use the latest Android Studio Beta, it will solve this issue. Also, if you're still here OP, please don't flag a workaround as correct answer, but rather the actual solution. — joe1806772, Jul 28 '21 at 12:52
this solved it for me in android studio: https://stackoverflow.com/a/70015429/859849 — jfaron, Jan 25 '22 at 19:41

score 915 · Accepted Answer · edited Nov 21 '21 at 07:08

915

First of all, I faced this issue in Android Studio 4.2.2 and you do not need to downgrade the SDK build tool from 31 to 30 or change compile SDK version.

The main problem is the two files missing in SDK build tool 31 that are:

dx.bat
dx.jar

The solution is that these files are named d8 in the file location so changing their name to dx will solve the error.

The steps are below.

For Windows

go to the location

 "C:\Users\user\AppData\Local\Android\Sdk\build-tools\31.0.0"

find a file named d8.bat. This is a Windows batch file.
rename d8.bat to dx.bat.
in the folder lib ("C:\Users\user\AppData\Local\Android\Sdk\build-tools\31.0.0\lib")
rename d8.jar to dx.jar

Remember AppData is a hidden folder. Turn on hidden items to see the AppData folder.

For macOS or Linux

# change below to your Android SDK path
cd ~/Library/Android/sdk/build-tools/31.0.0 \
  && mv d8 dx \
  && cd lib  \
  && mv d8.jar dx.jar

Now run your project.

edited Nov 21 '21 at 07:08

Aaron

854
2
11
22

answered Jul 18 '21 at 16:20

user16475264

9,190
2
2
3

25

Dug too deep to find an answer that doesn't require me to downgrade the API level. Instead of copying these files, I've created symlinks. This can be easily done from a command line: `mklink %ANDROID_HOME%\build-tools\31.0.0\dx.bat %ANDROID_HOME%\build-tools\31.0.0\d8.bat && mklink %ANDROID_HOME%\build-tools\31.0.0\lib\dx.jar %ANDROID_HOME%\build-tools\31.0.0\lib\d8.jar`. It's still a workaround though, but the cleanest one. – itachi Jul 19 '21 at 09:09
@mr_broccoli This should be the accepted answer. The marked answer is a workaround. – Abhinav Saxena Jul 21 '21 at 06:54
43

This should be the accepted answer. On Mac: `cd ~/Library/Android/sdk/build-tools/31.0.0 && mv d8 dx && cd lib && mv d8.jar dx.jar`. – Christopher Pickslay Jul 28 '21 at 01:17
46

unbelievable..... i just can't imagine why we need making such rename...what a shame.. – Oleg Jul 28 '21 at 06:00
tamhan@TAMHAN18:~/Android$ cd Sdk/build-tools/31.0.0/ tamhan@TAMHAN18:~/Android/Sdk/build-tools/31.0.0$ mv d8 dx tamhan@TAMHAN18:~/Android/Sdk/build-tools/31.0.0$ cd lib tamhan@TAMHAN18:~/Android/Sdk/build-tools/31.0.0/lib$ mv d8.jar dx.jar tamhan@TAMHAN18:~/Android/Sdk/build-tools/31.0.0/lib$ – Tam HANNA Aug 04 '21 at 20:03
That is been the only solution that has worked me after a full month of confusion with packets intermix and corrupt dependencies. thanks to you pal – Newtoxton Aug 15 '21 at 16:25
another way is to install another build-tools 29.0.3 then copy those dx.bat and dx.jar into build-tools 31.0.0 folder – Tung Do Sep 07 '21 at 05:06
4

`cd $ANDROID_HOME/build-tools/31.0.0; ln -s d8 dx; ln -s lib/d8.jar lib/dx.jar; ` – Joost Sep 09 '21 at 13:08
Should be the accepted answer, worked for me as well on Macos – cs.edoardo Sep 10 '21 at 12:25
1

Unfortunately no longer seems to work on Mac (Studio 2020.3.1 patch 2). There's only the d8 file, and renaming it to dx had no effect. There's no d8.jar file in that location. – Oscar Sep 24 '21 at 02:52
One culprit might be that the Gradle plug-in upgrade currently hangs forever, so it's stuck at some earlier version after other components have been updated. – Oscar Sep 24 '21 at 02:58
From this fix, it appears someone in the Android Studio team needs to rewrite/update their tests. – wandesky Sep 25 '21 at 07:27
14

How come such well known company release a product with such silly bugs? Releasing to the users without testing? Many people might have wasted their valuable time. – mvsagar Oct 07 '21 at 13:51
1

Yes, I think the same, it is the more portable workaround, valid for pipelines. In my case in Azure DevOps pipeline, I added a command line task to do the trick before the build. Thanks – rtrujillor Oct 08 '21 at 12:29
Tested and worked on Android Studio Arctic Fox 2020.3.1 Patch 3 with these settings `compileSdkVersion 31` `buildToolsVersion "31.0.0"` `targetSdkVersion 31` in the `AndroidManifests.xml` file. – Thiam Hooi Oct 15 '21 at 02:21
It worked like a charm on Mac! What a shame, that developing android has to be this buggy and such a hassle. – Arman Karimi Oct 22 '21 at 17:09
Perfect! Android Studio Arctic Fox | 2020.3.1 Patch 3 Build #AI-203.7717.56.2031.7784292 – chitgoks Nov 07 '21 at 02:17
this is working, thanks, but in my case not in appdata, i change file in sdk folder – mamena tech Nov 15 '21 at 11:07
@user16475264 this solution fixes my issue too!! Thanks a lot. But do you know if this is a "bug" that Android installer should fix? – Cupid Chan Nov 15 '21 at 15:56
1

I have the same issue with 32.0.0. The above solution works fine, just change the version from 31.0.0 to 32.0.0 in the command path ;) – Tomas Dec 10 '21 at 17:12
This is the problem that I've had for years with Android Studio... this type of fix (which NO ONE should have to do) happens ALL THE TIME with Android Studio. I'm constantly having to find weird hacks and fixes even to get simple projects to build. Google needs to step up their game. – Darren Gates Dec 17 '21 at 02:51
It worked for me in MacOS. Thank you so much – CR Sardar Feb 14 '22 at 23:39
Worked well for me. Thanks a lot... – Donnie Imafidon Feb 18 '22 at 18:17
Crazy that this was necessary. Worked for me using build tools version 33.0.0-rc2 – James Hooper Mar 21 '22 at 11:14
worked for me - Mac User Thanks – Avinash Ajay Pandey Mar 31 '22 at 13:58
It's so stupid we STILL have to do this. Thanks a lot, helped me fix build tools version `33.0.0-rc2` on macOS. – Arthur Khazbs Mar 31 '22 at 17:09
I confirm this works on Windows (11) too. I agree with whose who claim such hacky fix shouldn't be necessary on modern development environments. – Claudio Valerio Apr 12 '22 at 12:20
this is working, thanks!!!! – lord Apr 20 '22 at 00:24
This is **NOT** the correct solution, it is only a workaround. See [Andrey Alekseenko's answer](https://stackoverflow.com/a/68437642/2716245) for the correct solution. – Jim May 25 '22 at 06:58

score 125 · Answer 2 · edited Jul 27 '21 at 17:19

125

The same problem was encountered and solved with a few line changes.

Check the Project code panel, and go to Gradle Scripts → build.gradle file,

Change three places from 31 to 30: compileSdkVersion, buildToolsVersion, and targetSdkVersion
You'll notice a lightbulb hit occurring on modified lines. Click and choose sync [to version 30]. Android Studio will automatically download BuildTool V30 and change project settings.

Now run the app. It works for me.

edited Jul 27 '21 at 17:19

Peter Mortensen

30,030
21
100
124

answered Jul 15 '21 at 15:59

Jack Wang

1,487
1
7
3

1

If we are downgrading the build tools, it will work accepted but will not work with 31.0.0 – Abraham Mathew Jul 17 '21 at 07:21
36

Your answer is fine as a workaround. But it does not solve the actual problem if you have to work with SDK31 and build tools 31.0.0. In build tools 31.0.0, the following files "dx.bat" and "libs/dx.jar" are missing. The latest working build tools version was 31.0.0-rc4. To solve the problem in build tools 31.0.0, just copy the mentioned files from 31.0.0-rc4. However, even this is nothing more than a workaround. But at least this lets you work with build tools 31.0.0. – gal Jul 18 '21 at 10:49
@gal Everything works all good on local, but my CI seems to be complaining that it `Failed to find Build Tools revision 31.0.0-rc4` – CyberShark Aug 01 '21 at 13:48
1

@CyberShark That makes sense. If you work with other developers who all have to build the same project, then all of them need a working environment. So if you made a hack by copying the files "dx.bat" and "libs/dx.jar" from another build tools folder to build tools 31.0.0, then all others who work in the team must do the same. At the end, it's Google who should fix it in the next build tools version. – gal Aug 02 '21 at 15:08
This does not answer the question, it only provides a probably unacceptable tradeoff. Look at the highest voted answer for the working solution. – Teodor Sandu Sep 07 '21 at 22:05
Okay, Lets create a library and try this. worked it? – withoutOne Oct 28 '21 at 12:01

score 42 · Answer 3 · edited Jul 27 '21 at 17:37

42

The point is not to downgrade target API level, but to build exactly for API level 31 to prepare and test an app for Android 12!

It looks like DX is removed from SDK in favor of D8.

It looks like that Android Gradle plugin 4.x is not aware of that.

At the moment I see only two solutions:

To stay with AGP 4.x, one should copy DX from 30.0.3 to 31.0.0
Upgrade AGP to 7.x

edited Jul 27 '21 at 17:37

Peter Mortensen

30,030
21
100
124

answered Jul 19 '21 at 08:50

Andrey Alekseenko

421
3
3

3

That is the solution, another answer is only to patch not an actual solution of the problem. Thank you very much for sharing. – Hitesh Dhamshaniya Jul 29 '21 at 17:36
3

To clarify, it appears (from my testing) that Build Tools 31 and up are **incompatible** with AGP 4.x and below. With AGP 4.x, stay with Build Tools 30.0.3 (it seems to build with SDK 31 fine). Once you have upgraded to AGP 7.x (and Gradle 7), you can use Build Tools 31 or 32 without any issues. – big_m Dec 14 '21 at 14:14
Unfortunately, upgrading AppCompat to 1.4 requires to compile against API 31. – Konsumierer Dec 21 '21 at 07:56
That's the only correct solution in this topic and this should be the accepted answer. – pablo432 Apr 12 '22 at 11:10

score 30 · Answer 4 · edited Sep 05 '21 at 08:07

30

The solution for Mac is pretty similar to Windows, yet not fully conclusive from reading the Windows solution. The paths and file names are different, but the problem is basically the same.

Open the terminal application and type the commands below
Hit Enter after every command line you type to execute the command
Type cd /Users/admin/Library/Android/sdk/build-tools/
Attention: Your user directory name may be different from "admin"
Navigate to the corresponding version: type cd 31.0.0
Type cp d8 dx
Type cd lib
Type cp d8.jar dx.jar

This fixed my issues on macOS v10.13.6 (High Sierra).

edited Sep 05 '21 at 08:07

Peter Mortensen

30,030
21
100
124

answered Jul 30 '21 at 23:09

Chris S.

939
10
24

2

that is awesome real solution. this worked for me with macOS Monterey IntelliJ IDEA ultimate API31. Downgrading to lower api is not solution. – withoutOne Nov 16 '21 at 19:51
1

This is a more recent solution. Worked for me with 32.0.0 Thanks! – Team chang Jan 07 '22 at 20:38
worked for me !! – S.M_Emamian Apr 16 '22 at 11:13

score 20 · Answer 5 · edited Jul 27 '21 at 17:22

After changing these settings, it seems to work fine. I downloaded SDK version 30 from SDK Manager.

android {
    compileSdkVersion 30
    buildToolsVersion "30.0.3"
    defaultConfig {
        applicationId "com.anurag.myapplication"
        minSdkVersion 23
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

score 17 · Answer 6 · answered Jul 21 '21 at 14:10

In order to fix the issue, firstly go to the following location:

C:\Users\User\AppData\Local\Android\Sdk\build-tools\31.0.0

Then find the file d8 (Windows batch file) and rename it to dx.

Then go to:

C:\Users\User\AppData\Local\Android\Sdk\build-tools\31.0.0\lib

Then find the file d8 (Executable Jar File) and rename is to dx.

Your problem will be solved now.

Archimedes Trajano · Answer 7 · 2021-07-30T13:45:17.087

16

For those who are using Azure DevOps and require things to work with 30.0.3 you need to uninstall version 31.0.0

I added this to my pipeline to make my builds work again.

  - bash: |
      $ANDROID_SDK_ROOT/tools/bin/sdkmanager --uninstall 'build-tools;31.0.0'

The environment variable $ANDROID_SDK_ROOT is in the preset variables

edited Jul 30 '21 at 13:45

answered Jul 22 '21 at 16:50

Archimedes Trajano

28,830
14
134
195

What path do you set for ANDROID_SDK_ROOT? – H_H Jul 30 '21 at 13:02
In my case it was Windows - https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md – H_H Jul 30 '21 at 14:21
side question, is Windows agent faster to build Android? – Archimedes Trajano Jul 30 '21 at 15:03
Nope, I don't think. I build ionic cordova app and it take 25-30 min. – H_H Jul 30 '21 at 15:59
FWIW, I was trying to make Ionic + cordova builds working with Fastlane on Github Actions and this did the trick. – Kevin Boosten Aug 02 '21 at 20:36

score 13 · Answer 8 · edited Jul 27 '21 at 17:32

Version 31.0.0 itself is corrupt, and we need to downgrade to 30.

Steps I followed for the same:

Open project structure → press Ctrl + Alt + Shift + S
Go to Module → properties → *Compiled SDK Version: 30 Build Tools Version: 30.0.2
Go to Default Config → Target SDK Version: 30
Apply and Close.
Menu Tools → SDK Manager
Uncheck API 31 to uninstall and check Android 11.0(R) to install (30.0.3) in my case.
Apply.

score 9 · Answer 9 · edited Jul 27 '21 at 17:25

9

If you carefully look at the logs you'll see:

Build-tool 31.0.0 is missing DX at path-to-sdk\build-tools\31.0.0\dx.bat

You can try copying it from previous versions, but that won't lend well if you have to tell your entire team to do the same and it still fails on your server pipeline. This happened to me on 31.0.0-rc5 release as well.

edited Jul 27 '21 at 17:25

Peter Mortensen

30,030
21
100
124

answered Jul 15 '21 at 05:15

Ramin

454
6
20

In my case, not only `dx.bat`, but `dx.jar` too which placed in `/build-tools/lib`; – Akbolat SSS Nov 07 '21 at 08:52
build-tools path on MacOS: `/Users/username/Library/Android/sdk` – Akbolat SSS Nov 07 '21 at 09:00

score 7 · Answer 10 · edited Jul 27 '21 at 17:42

7

In file build.gradle (Module: HelloWorld.app):

compileSdkVersion 30
buildToolsVersion "30.0.0"
targetSdkVersion 30

Change the above configuration to this:

edited Jul 27 '21 at 17:42

Peter Mortensen

30,030
21
100
124

answered Jul 22 '21 at 10:14

vinay shetty

625
7
13

score 6 · Answer 11 · answered Feb 13 '22 at 13:13

Change your Gradle build from :

android {
    compileSdkVersion 31
    buildToolsVersion '31.0.0'

    defaultConfig {
        applicationId "com.example.eg"
        minSdkVersion 23
        targetSdkVersion 31
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

to:

android {
    compileSdk 31

    defaultConfig {
        applicationId "com.example.eg"
        minSdk 23
        targetSdk 31
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

This will work

score 5 · Answer 12 · edited Sep 05 '21 at 08:04

5

I downloaded dx.bat file from https://android.googlesource.com/platform/dalvik/+/master/dx/etc/dx.bat.

I put it in \build-tools\31.0.0 and then downloaded the dx.jar file (which was also missing, by the error message I got) from http://www.java2s.com/Code/Jar/d/Downloaddxjar.htm.

I put it into directory \build-tools\31.0.0\lib.

Then it worked.

edited Sep 05 '21 at 08:04

Peter Mortensen

30,030
21
100
124

answered Aug 22 '21 at 05:31

Yuval A.

5,444
11
49
63

score 4 · Answer 13 · answered Jul 16 '21 at 13:29

First of all, guys if you're facing these types of issues you can try the solution where we need to shift 31 to 30. And after that some important steps are required to do: Step:

To open project structure > Press Ctrl+Alt+Shift+S
Open Module > properties > Compiled Sdk Version: 30 Build Tools Version: 30.0.2
Click on Default Config > Target SDK Version: 30

After that, your task is not, in some cases still, you can see this configuration is not accepted, you need to do these steps also:

Go to the top Right area, and click on SDK Manager Icon.
Select Android SDK > image 1 where you need to tick all Android version which you need*
After tick Click OK and then install.
Android SDK > SDK Tool > right down side > show Package detail > tick on 30.0.2 option and then install. image 2 > select 30.0.2

5) Now done click OK install> apply your good to go.

Dmitry · Answer 14 · 2022-01-15T16:24:47.187

4

I don't have enough reputation for commenting yet, but there is the solution with symbolic links for Windows, and I'd like to add that it works for macOS, too.

That's the command for Mac's terminal:

ln %ANDROID_HOME%/sdk/build-tools/31.0.0/d8 %ANDROID_HOME%/sdk/build-tools/31.0.0/dx && ln %ANDROID_HOME%/sdk/build-tools/31.0.0/lib/d8.jar %ANDROID_HOME%/sdk/build-tools/31.0.0/lib/dx.jar

edited Jan 15 '22 at 16:24

answered Jul 20 '21 at 09:43

Dmitry

81
6

score 4 · Answer 15 · answered Jul 21 '21 at 13:16

4

To uninstall only Build-Tools 31.0.0 from Android Studio

Navigate to:
Configure -> SDK Manager -> SDK Tools [tab] -> Show Package Details [check box]
click on Android SDK Build-Tools 31
uncheck 31.0.0
and Hit OK

answered Jul 21 '21 at 13:16

Sachin Chillal

113
6

score 3 · Answer 16 · edited Sep 05 '21 at 08:08

3

I unistalled and installed the 31.0.0 package and still it was showing the error.

I used RC2 build tools and it compiled and ran fine without downgrading to SDK version 30.

In file app/build.gradle:

buildToolsVersion "31.0.0-rc2"

edited Sep 05 '21 at 08:08

Peter Mortensen

30,030
21
100
124

answered Jul 24 '21 at 10:06

Monster Brain

1,798
19
28

score 3 · Answer 17 · answered Sep 10 '21 at 07:26

My Android Studio Arctic Fox 2020.3.1 Patch 2
with
downloaded Android 12 and Android SDK Build-Tools 31 in Android SDK

working with buildToolsVersion "31.0.0"

build.gradle (Project)

buildscript {
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath "com.android.tools.build:gradle:7.0.2"
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.30"
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

build.gradle (Module)

plugins {
    id 'com.android.application'
    id 'kotlin-android'
}

android {
    compileSdk 31
    buildToolsVersion "31.0.0"

    defaultConfig {
        applicationId "com.example.android12"
        minSdk 21
        targetSdk 31
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    kotlinOptions {
        jvmTarget = '1.8'
    }
}

dependencies {

    implementation 'androidx.core:core-ktx:1.6.0'
    implementation 'androidx.appcompat:appcompat:1.3.1'
    implementation 'com.google.android.material:material:1.4.0'
    implementation 'androidx.constraintlayout:constraintlayout:2.1.0'
    testImplementation 'junit:junit:4.+'
    androidTestImplementation 'androidx.test.ext:junit:1.1.3'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.4.0'
}

gradle-wrapper.properties

#Fri Sep 10 13:52:36 ICT 2021
distributionBase=GRADLE_USER_HOME
distributionUrl=https\://services.gradle.org/distributions/gradle-7.0.2-bin.zip
distributionPath=wrapper/dists
zipStorePath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME

score 2 · Answer 18 · edited Jul 27 '21 at 17:28

2

I unchecked 31 under the SDK Manager, clicked Android 11.0(R) to revert back to 30, and updated the Build Gradle (project) to change compileSdkVersion and targetSdkVersion from 31 to 30.

I also had to update buildToolsVersion to "30.0.2" instead of 30. Now it works.

edited Jul 27 '21 at 17:28

Peter Mortensen

30,030
21
100
124

answered Jul 15 '21 at 18:14

Meg

21
1

Mubtasim Fuad · Answer 19 · 2021-07-15T23:44:40.830

2

Press Ctrl+Alt+Shift+S to open project structure. The select Module from the left.

Open Properties tab and change the followings:
Compiled Sdk Version: 30
Build Tools Version: 30.0.2

After that open Default Config tab and change:
Target SDK Version: 30

edited Jul 15 '21 at 23:44

answered Jul 15 '21 at 23:37

Mubtasim Fuad

161
1
4

score 2 · Answer 20 · edited Jul 27 '21 at 17:41

2

Try to reinstall the SDK 31 again and restart Android Studio, it should work. Otherwise, from the SDK Manager, install the SDK 30 to the System and configure the app build Gradle file as

compileSdkVersion 30
buildToolsVersion "30.0.0"
defaultConfig {
    targetSdkVersion 30
}

edited Jul 27 '21 at 17:41

Peter Mortensen

30,030
21
100
124

answered Jul 21 '21 at 09:57

neelkanth_vyas

152
7

score 2 · Answer 21 · edited Jul 27 '21 at 17:43

It's a conflict issue with Android studio and SDK 31.

Convert your build.gradle file like this:

android {
    compileSdkVersion 30
    buildToolsVersion "30.0.3"

    defaultConfig {
        applicationId "com.example.app"
        minSdkVersion 21
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }
}

score 2 · Answer 22 · edited Sep 05 '21 at 08:07

2

There are so many wrong and misleading answers here.

The only thing you should really do is to install the latest Android Studio Beta version if you're using the Beta SDK. With the latest Android Studio Beta comes support for the latest AGP, which correctly supports SDK 31.

edited Sep 05 '21 at 08:07

Peter Mortensen

30,030
21
100
124

answered Jul 28 '21 at 12:50

joe1806772

446
6
19

score 2 · Answer 23 · answered Sep 26 '21 at 07:51

In build.gradle(Module) file. Change the following settings.

android {
    compileSdkVersion 30
    buildToolsVersion "30.0.0"

    defaultConfig {
        applicationId "com.recycleview.mvvm"
        minSdkVersion 16
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

score 2 · Answer 24 · answered Mar 31 '22 at 11:25

You don't need to specify android.buildToolsVersion from Build Tools 27.0.3 or higher.

Build Tools 27.0.3 or higher. Keep in mind, you no longer need to specify a version for the build tools using the android.buildToolsVersion property—the plugin uses the minimum required version by default.

Source (Developers.Android)

score 1 · Answer 25 · edited Sep 10 '21 at 04:55

1

I first followed user16475264's answer, but the real issue (at least in my case) turned out to be the version of the AGP (Android Gradle Plugin). So, after upgrading to v7, I rolled back my changes for both, the executable and the JAR file: dx -> d8 in ~/Library/Android/sdk/build-tools/31.0.0. This worked

edited Sep 10 '21 at 04:55

Peter Mortensen

30,030
21
100
124

answered Sep 09 '21 at 21:24

ddsultan

1,755
17
16

Which one did you change to here? be specific – TheRealChx101 Jan 05 '22 at 16:33
@TheRealChx101, by default (with my Android Studio version) the AGP (Android Gradle Plugin) was `4.x` and I followed user16475264's answer but after upgrading to `v7` that original problem was gone so I rolled back what I had done with user16475264's answer. – ddsultan Jan 05 '22 at 17:56

score 0 · Answer 26 · edited Sep 05 '21 at 08:02

0

Check your Gradle build:

android {
    compileSdkVersion 30
    buildToolsVersion "31.0.0" // Solution 1: // Downgrade it to 30.0.3

    defaultConfig {
        applicationId "com.mobiz.lottotemplate440"
        minSdkVersion 21
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

Or,

Solution 2

Download SDK 31 from SDK manager.

edited Sep 05 '21 at 08:02

Peter Mortensen

30,030
21
100
124

answered Aug 11 '21 at 17:21

AMJAD AFRIDI

21
2

What file? *build.gradle*? – Peter Mortensen Sep 05 '21 at 08:09
Build.gradle (app) – AMJAD AFRIDI Oct 09 '21 at 08:41

score 0 · Answer 27 · answered Sep 01 '21 at 18:21

There are multiple solutions to this issue though one which should logically fix it does not work i.e. uninstalling build tool version 31.0.0 and reinstalling that. This solution does not work and Android Studio team probably need to look into it.

Currently which seems to work is: Solution 1 (Downgrade Build Tool Version being used in project)

Check the Project code panel, and go to Gradle Scripts –> build.gradle file,

Change 3 places: compileSdkVersion, buildToolsVersion, targetSdkVersion from 31 to 30 You’ll notice a lightbulb hit occurring on modified lines, click and choose sync [to version 30]. The Android Studio will automatically download BuildTool V30 and change project settings.

Solution 2 (Get missing dx.bat and dx.jar files from previous version build tools) Build-tool 31.0.0 is missing DX at path-to-sdk\build-tools\31.0.0\dx.bat and Build-tool 31.0.0 is missing DX at path-to-sdk\build-tools\31.0.0\lib\dx.jar

You can try copying it from previous version build tools. I did from Version 30.0.3 and it worked for me.

score 0 · Answer 28 · edited Sep 08 '21 at 00:07

I tried uninstalling tool 31 from the SDK manager. It successfully did so, but when building a project, it will reinstall and the same problem happens.

Then I tried the rename d8 to dx suggestion. And it starts running a bunch of tasks and causes the entire computer to hang. Seeing as how the project is just a simple activity. I'm not sure why Gradle needs to constantly connect to the Internet and take up so much of CPU usage.

After a hard reboot and fsck later, the project builds fine.

score 0 · Answer 29 · answered Oct 09 '21 at 04:56

0

Upgrade gradle to 7.0.2 might helps

answered Oct 09 '21 at 04:56

kevinzhow

64
5

score 0 · Answer 30 · answered Oct 19 '21 at 14:46

0

go to android studio setting->android SDK-> SDK tools-> in the list mark google play licensing and apply. it will download you a file and then sync your project and it's done.

answered Oct 19 '21 at 14:46

Bagher

29
3

score 0 · Answer 31 · answered Apr 12 '22 at 14:54

I answered this question over here, but I'll copy/paste the answer as it's relevant:

As pointed out in other issues, the problem is that dx (or dx.bat) is no longer available. This was a purposeful change announced in 2018.

Suggested resolutions of renaming d8 to dx or copying it from build tools 30.0.0 will resolve the issue, but dx isn't likely to return. So you'll be stuck patching every build tools installation on every developer's machine going forward.

The more forward-compatible solution is to upgrade your Android gradle plugin. This isn't as straightforward as just changing the number in gradle, but I find that Android Studio's upgrade process works well for my projects. If you open your project-level build.gradle file, open up the quick fixes menu from the lightbulb over your

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

section. From here, choose to upgrade to the newest possible version (not just 4.x in my case).

Then I run the upgrade steps for literally everything:

My issue was Unity specific though: I needed to use the system Android SDK rather than the one built in, but Unity itself likes to regenerate these build files and will just grab the newest buildtools it can find. To reduce manual steps and to avoid having to export my project, I instead chose to generate my module-level build.gradle files from my "Player Settings>Publishing Settings" window:

Both files will have a line that looks like:

buildToolsVersion '**BUILDTOOLS**'

Which you can replace with:

buildToolsVersion '30.0.0'

From Unity, this lets me build and deploy projects as I had before without modifying the buildtools installation.

Android Studio error "Installed Build Tools revision 31.0.0 is corrupted"

31 Answers31

For Windows

For macOS or Linux

To uninstall only Build-Tools 31.0.0 from Android Studio

Solution 2

Linked

Related