'Execution failed for task ':app:checkDebugAarMetadata'
I am getting this error while running my app.
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Could not find com.android.support.constraint:constraint-layout:1.1.3.
Searched in the following locations:
- https://jcenter.bintray.com/com/android/support/constraint/constraint-layout/1.1.3/constraint-layout-1.1.3.pom
If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
Required by:
project :app
> Could not find com.android.support:appcompat-v7:25.3.1.
Searched in the following locations:
- https://jcenter.bintray.com/com/android/support/appcompat-v7/25.3.1/appcompat-v7-25.3.1.pom
If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
Required by:
project :app
> Could not find com.android.support:support-v4:25.3.1.
Searched in the following locations:
- https://jcenter.bintray.com/com/android/support/support-v4/25.3.1/support-v4-25.3.1.pom
If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
Required by:
project :app
> Could not find com.android.support:design:25.3.1.
Searched in the following locations:
- https://jcenter.bintray.com/com/android/support/design/25.3.1/design-25.3.1.pom
If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
Required by:
project :app
Possible solution:
- Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html
Solution 1:[1]
I already had the compileSdkVersion and targetSdkVersion on version number 30.
I added to build.repositories jcenter() and to allprojects.repositories jcenter(), after that I build the react-native app and it works fine.
My build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext {
buildToolsVersion = "30.0.2"
minSdkVersion = 21
compileSdkVersion = 30
targetSdkVersion = 30
ndkVersion = "20.1.5948944"
}
repositories {
google()
mavenCentral()
jcenter()
}
dependencies {
classpath("com.android.tools.build:gradle:4.2.1")
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
mavenCentral()
mavenLocal()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url("$rootDir/../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
google()
jcenter()
maven {
// All of the Detox artifacts are provided via the npm module
url("$rootDir/../../../node_modules/detox/Detox-android")
}
}
}
Solution 2:[2]
For our Flutter Project: Navigate to app-level build.gradle file. Change compileSdkVersion from 30 to 31 and Change targetSdkVersion from 30 to 31
Solution 3:[3]
Solution 4:[4]
Update 2021.07
I just had to change the compileSdkVersion and targetSdkVersion in my build.gradle file. (YourApp\android\build.gradle).
compileSdkVersion from 29 to 30 targetSdkVersion from 29 to 30
after this change, it started to run.
Credit: https://exerror.com/solved-execution-failed-for-task-appcheckdebugaarmetadata/
Solution 5:[5]
Seems you are using newer version of Android Studio and your implementation is missing or using deprecated libraries. Otherwise, you could try the following implementation in your build.gradle (Module: app) files:
dependencies {
def appcompat_version = "1.2.0"
// ...
implementation 'com.google.android.material:material: 1.2.1'
implementation "androidx.constraintlayout:constraintlayout:2.0.2"
implementation "androidx.appcompat:appcompat:$appcompat_version"
implementation "androidx.appcompat:appcompat-resources:$appcompat_version"
implementation "com.android.support:support-core-utils:28.0.0"
// ...
}
Solution 6:[6]
This error "Could not resolve all files for configuration ':app:debugRuntimeClasspath" is due to a network failure
It is because Android studio doesn't have full access to internet connection which is caused by another application controlling your proxy. E.g Charles Proxy.
Solution:
- Stop/Close any proxy application on your computer.
- Rebuild the project
Solution 7:[7]
I don't know why but somehow my gradle offline mode was turned on after android studio 4.1.1 update and this caused the problem. make sure that that thing is not turned on!
Solution 8:[8]
android>build.gradle
!Check versions properly
buildscript {
ext {
buildToolsVersion = "29.0.3"
minSdkVersion = 21
compileSdkVersion = 29
targetSdkVersion = 29
ndkVersion = "20.1.5948944"
googlePlayServicesVersion = "17.0.0"
}
repositories {
...
}
dependencies {
...
}
}
Solution 9:[9]
reactnative/node_modules/react-native-reanimated/android/react-native-reanimated-6*.aar. Just go to the above path and copy the files and rename what is required, For example, if the problem is not finding 66.aar copy & paste the previous main aar file and hermen aar file in the path and rename it with 66
Solution 10:[10]
maybe you didnt install one module correctly
check all module installing documentation
I found that I installed react-native-reanimated incorrectly and after going throught documentation https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/installation
the error was fixed
Solution 11:[11]
Solution 12:[12]
Mostly this happens on your 1st time running of project /or running in a new device , Fix
- Make sure you have proper internet connection
- If not fixed then trun of auto detect setting in proxi setting of your pc
Solution 13:[13]
I think first you run create apk file cmd and then run build cmd. problem solved.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow


