Fixing the "4 issues were found when checking AAR metadata" Error

The error Execution failed for task ':app:checkDebugAarMetadata' is a common but frustrating build failure in Android Studio. It indicates a problem with the metadata of one or more Android Archive (AAR) libraries your project depends on.

This guide will help you diagnose the root cause and provide step-by-step solutions to resolve it.

Step 1: Diagnose the Problem

The error message is generic. To find the specific culprit, you need more detailed logs.

Open the Terminal in Android Studio (View > Tool Windows > Terminal).
Run one of the following commands to get verbose output:
bash

./gradlew :app:checkDebugAarMetadata --info

or for even more detail:

bash

./gradlew :app:checkDebugAarMetadata --debug

Scan the output for lines containing "AAR metadata" or specific library names. The log will explicitly tell you which library is causing the issue and why (e.g., minSdkVersion mismatch).

Step 2: Apply the Fix (Based on the Cause)

Once you've identified the problematic library, apply the relevant solution.

🔧 Fix 1: minSdkVersion Mismatch (Most Common)

This occurs when a library requires a higher minimum Android version than your app.

Solution A (Recommended): Raise your app's minSdkVersion to meet the library's requirement.
Open your app/build.gradle file and update the value:
gradle

android {
    defaultConfig {
        minSdkVersion 21 // <-- Increase this number
        targetSdkVersion 34
    }
}

Solution B (Use with Caution): Forcefully override the check for a specific library. Warning: This can cause runtime crashes on older devices if the library uses unsupported APIs.
Add this to your AndroidManifest.xml:

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
          xmlns:tools="http://schemas.android.com/tools">

    <uses-sdk tools:overrideLibrary="com.problematic.library.package.name" />
    <!-- Replace with the actual library's package name -->

    <application ...> ... </application>
</manifest>

Fix 2: Corrupted Cache or AAR File

Sometimes, the downloaded library files get corrupted.

Clean your project: Build > Clean Project in Android Studio or run ./gradlew clean in the terminal.
Invalidate Caches: Go to File > Invalidate Caches / Restart... and select Invalidate and Restart.
Delete Gradle cache manually:
- Windows: C:\Users\[YourUsername]\.gradle\caches
- macOS/Linux: ~/.gradle/caches
- Delete the modules-2 and transforms-X folders inside. Gradle will re-download everything on the next build.

🔧 Fix 3: Incompatible Dependencies

Your project's library versions might conflict with each other or with your build tools.

Update everything: Ensure your Android Gradle Plugin (AGP), Gradle version, and libraries are compatible and up-to-date.
- Project-level build.gradle:
  gradle

plugins {
    id 'com.android.application' version '8.9.1' apply false // Use latest stable version
}

gradle-wrapper.properties:

distributionUrl=https\://services.gradle.org/distributions/gradle-8.11.1-bin.zip

App-level build.gradle:

android {
    compileSdk 36
    // ...
}

Downgrade strategically: If you can't update your build tools, try downgrading the problematic library to the last compatible version. For example, if androidx.core is the issue:

dependencies {
    implementation "androidx.core:core:1.16.0"
    implementation "androidx.core:core-ktx:1.16.0"
}

Summary and Recommendation

First, always run ./gradlew --info to identify the exact library and error.
The most common fix is to increase your app's minSdkVersion in build.gradle.
If you're starting a new project or can update, upgrading your Android Gradle Plugin (AGP) and compileSdk is the best long-term solution.
Use the overrideLibrary manifest flag only as a last resort if you fully understand the risks.

By methodically following these steps, you can resolve the AAR metadata error and get your build back on track.

ITCanopy

How to Fix "4 issues were found when checking AAR metadata" in Android Studio