How can I resolve the error "The minCompileSdk (31) specified in a dependency's AAR metadata" in native Java or Kotlin?

Question

The error message:

The minCompileSdk (31) specified in a dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties) is greater than this module's compileSdkVersion (android-30). Dependency: androidx.core:core-ktx:1.7.0-alpha02.

AAR metadata file:
C:\Users\mohammad.zeeshan1.gradle\caches\transforms-2\files-2.1\a20beb0771f59a8ddbbb8d416ea06a9d\jetified-core-ktx-1.7.0-alpha02\META-INF\com\android\build\gradle\aar-metadata.properties.

(The proposed dupe, unlike this question, has an MCVE) – Zoe stands with Ukraine Sep 23 '21 at 14:35 — Zoe stands with Ukraine, Sep 23 '21 at 14:35

score 194 · Answer 1 · answered Sep 05 '21 at 21:51

194

Set both compileSdkVersion and targetSdkVersion to 31 in your build.gradle(app) file.

android {
    compileSdkVersion 31 // <-- This
    defaultConfig {
        applicationId "com.example.app"
        targetSdkVersion 31 // <-- and this too
        // ...
    }
}

answered Sep 05 '21 at 21:51

CopsOnRoad

175,842
51
533
380

4

CHECK THIS LIBRARY: implementation 'androidx.appcompat:appcompat:1.4.0' CHANGUE TO 1.3.1 VERSION. And fixed with resolutionStrategy { force 'androidx.core:core:1.6.0' } also.. – FreddicMatters Nov 24 '21 at 00:26
6

Gradle build is failing after I change this to 31. – Mooncrater Dec 02 '21 at 14:43
3

Changing to Compile SDK version to 31 worked for me – bharat udasi Apr 19 '22 at 06:41
This works for me after also updating ext.kotlin_version inside gradle's build.gradle file to the latest version. – chowmein May 13 '22 at 02:09

score 123 · Accepted Answer · edited Jan 01 '22 at 18:08

123

I have found the solution. Enter this line of code above package in the app Gradle file.

For Kotlin developers:

configurations.all {
    resolutionStrategy { force 'androidx.core:core-ktx:1.6.0' }
}

For Java developers

configurations.all {
    resolutionStrategy { force 'androidx.core:core:1.6.0' }
}

edited Jan 01 '22 at 18:08

Peter Mortensen

30,030
21
100
124

answered Sep 03 '21 at 10:51

Mohammad Zeeshan

3,517
4
9
15

1

For java developers, remove the `ktx`: `resolutionStrategy {force 'androidx.core:core:1.6.0'}` – Zain Sep 18 '21 at 23:39
2

I'm still getting the same issue on ReactNative. Adding this line didn't work out in my project. Is there more way to solve this issue? – Ayush Katuwal Sep 21 '21 at 05:36
1

Why does this work? I'm really surprised; my project gradle defines the kotlin version as 1.5.10! – SMBiggs Nov 09 '21 at 20:35
1

Why do this rather than just downgrade the core-ktx version to 1.6.0? - I am a mobile noob... – Paul Barclay Nov 17 '21 at 10:42
5

With Arctic Fox this hack no longer seems to work. I had to bump up the compileSdk from 30 to 31 in build.gradle (app), as mentioned in this answer https://stackoverflow.com/a/69283902/624814. – SMBiggs Dec 06 '21 at 16:25
1

No longer works on Arctic Fox. Android Development is a such a pain in @$$. – Udayaditya Barua Dec 11 '21 at 06:50
2

It doesn't even work anymore when creating a default Android project from scratch with a newly installed IntelliJ IDEA. They went from a great tool to something unusable. – RedGlyph Dec 31 '21 at 10:36

Abandoned Cart · Answer 3 · 2022-05-14T12:10:46.893

47

This issue is most often seen with libraries that declare

implementation androidx.core:core-ktx:1.7.0-beta01

The minCompileSdk is 31, but the minSdkVersion is significantly lower.

Increasing the compileSdk of your project is enough to fix the issue. There is no need for overrides or even changing the targetSdk.

android {
    compileSdk 31

...
}

edited May 14 '22 at 12:10

answered Sep 22 '21 at 12:07

Abandoned Cart

3,966
1
31
36

1

Greate answer. This is the correct solution regarding this issue. Due to fix this issue we can change compile sdk enough. If we change targetSdk then, it will give some other ploblems, thats not need for this issue fix. – Mohamed Ibrahim Jan 04 '22 at 04:38
1

This Answer fixed my issue. – Gautham Vijayan May 13 '22 at 03:46

score 38 · Answer 4 · edited Jan 01 '22 at 18:04

38

Finally, I can solve my issue.

What was the problem?

I had the following dependency in one module -

implementation "androidx.core:core-ktx:+"

but other modules, including the app module, had the following dependency

implementation "androidx.core:core-ktx:1.6.0"

Converting

implementation "androidx.core:core-ktx:+"

to

implementation "androidx.core:core-ktx:1.6.0"

solved my problem.

edited Jan 01 '22 at 18:04

Peter Mortensen

30,030
21
100
124

answered Sep 03 '21 at 05:17

Saiful Islam Sajib

1,833
10
16

2

For me it was suggesting version 1.6.0 as soon as I cleared the "+" and it then compiled with that version. So I think you should check for the auto suggestion and use this value then. – tickietackie Sep 17 '21 at 14:12

score 11 · Answer 5 · edited Jan 01 '22 at 17:57

11

You're going to need to update your compile SDK to 31. It sounds like it's currently set to 30. In your Gradle files there should be something like compileSdk in the android block.

Bump that up to 31. If that's an issue for some reason, you can also bump down your dependencies to versions that don't require that compile SDK version.

edited Jan 01 '22 at 17:57

Peter Mortensen

30,030
21
100
124

answered Sep 02 '21 at 18:19

Nathan K

159
7

4

Is there any other solution? I can't do this because some dependencies break after doing this. – Rohit Aggarwal Sep 03 '21 at 04:59
3

Facing same problem .. any solution keeping my compile sdk version 30 ? – Saiful Islam Sajib Sep 03 '21 at 05:06
use implementation "androidx.core:core-ktx:1.3.0" – Islam Alshnawey Sep 13 '21 at 17:03

score 10 · Answer 6 · edited Jan 01 '22 at 22:21

10

When using Jetpack Compose navigation, I had this problem...

I was using androidx.navigation:navigation-compose:2.4.0-alpha07

So I solved it by using another version:

`androidx.navigation:navigation-compose:2.4.0-alpha06`

edited Jan 01 '22 at 22:21

Peter Mortensen

30,030
21
100
124

answered Sep 07 '21 at 13:25

Mahdi nezam parast

343
1
8

The problem exists in alpha07 and alpha08. Changing it to 06 fixed my problem. (I wanted to compile it with SDK 30, but never versions require SDK 31) – ShadeToD Sep 09 '21 at 12:46
Downgrading version is not a good solution. – Vikash Parajuli Jun 01 '22 at 05:47

score 9 · Answer 7 · edited Jan 01 '22 at 18:10

I had this issue on a react-native project that was working a few days ago, suddenly I get this error:

* What went wrong:
Execution failed for task ':app:checkDevDebugAarMetadata'.
> Multiple task action failures occurred:
   > A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
      > The minCompileSdk (31) specified in a
        dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
        is greater than this module's compileSdkVersion (android-30).
        Dependency: androidx.core:core-ktx:1.7.0-alpha02.
        AAR metadata file: /Users/me/.gradle/caches/transforms-2/files-2.1/ed22ee8b86d25659bbef1e9ee203b75c/jetified-core-ktx-1.7.0-alpha02/META-INF/com/android/build/gradle/aar-metadata.properties.
   > A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
      > The minCompileSdk (31) specified in a
        dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
        is greater than this module's compileSdkVersion (android-30).
        Dependency: androidx.core:core:1.7.0-alpha02.
        AAR metadata file: /Users/me/.gradle/caches/transforms-2/files-2.1/23234efc7e9de9bfe6a3fea85a6072ef/core-1.7.0-alpha02/META-INF/com/android/build/gradle/aar-metadata.properties.

After reading the error message I understood that the problem was androidx.core:core-ktx so I searched more about it and found that a new version has just been released last September 01 https://androidx.tech/artifacts/core/core-ktx/ which was https://androidx.tech/artifacts/core/core-ktx/1.7.0-alpha02 which has targetSdkVersion = 31

I ran grep -r "androidx.core:core-ktx" node_modules and found that I have one dependency that has implementation "androidx.core:core-ktx:+" which will install the latest version when I install the app. I can't just update to 31 because it seems to break the codes of some of my dependencies, I will get:

unrecognized Attribute name MODULE (class com.sun.tools.javac.util.SharedNameTable$NameImpl)

Which I don't really know how to fix and can't find any lead, it's most probably because it's new.

As a workaround, on file android/app/build.gradle

Add the following block on before android {} block.

configurations.all {
    resolutionStrategy { force 'androidx.core:core-ktx:1.7.0-alpha01' }
}

After doing this, it worked for me. It will force all androidx.core:core-ktx to be 1.7.0-alpha01

I ran `grep -r "androidx.core:core-ktx" node_modules` and got no output. Still I am getting this error. — Rohit Aggarwal, Sep 05 '21 at 17:26
I just had this error while building for android on my react-native project, it wasn't due to `androidx.core:core-ktx` but instead due to `androidx.browser:browser`. This comes from the library `react-native-inappbrowser-reborn`, which specifies the android package version to be 1+. After a gradle sync, `androidx.browser` version 1.4.0-alpha01 is brought in, causing this error. A fix is suggested here https://github.com/proyecto26/react-native-inappbrowser/issues/298 — Tin Nguyen, Sep 18 '21 at 16:41
For what it's worth, the error you received about MODULE etc will resolve with JDK11, JDK8 does not work well with the API31 android sdk levels — Mike Hardy, Nov 04 '21 at 22:17

score 4 · Answer 8 · edited Jan 01 '22 at 22:24

4

I had the same issue and found out the issues was with the lifecycle library.

I changed from the beta version,

androidx.lifecycle:lifecycle-livedata:2.4.0beta1

to current stable version,

androidx.lifecycle:lifecycle-livedata:2.3.1

Check the Android website for versions.

edited Jan 01 '22 at 22:24

Peter Mortensen

30,030
21
100
124

answered Sep 18 '21 at 21:18

Paul Kunda

51
2

Now even the new stable release 2.4.0 is throwing this error. – Udayaditya Barua Nov 22 '21 at 12:45
This is the only solution that worked for me without increasing compile version. Thanks – Oguz Ozcan Dec 08 '21 at 16:14

How can I resolve the error "The minCompileSdk (31) specified in a dependency's AAR metadata" in native Java or Kotlin?

8 Answers8

Linked