Skip to content
Related Articles

Related Articles

Improve Article

How to Fix Gradle: Execution failed for task ‘:processDebugManifest’ Error in Android Studio?

  • Last Updated : 16 Jun, 2021
Geek Week

Gradle assemble-info provided me an indication that the manifestations do not have various versions of SDK and can not be integrated. And after hours of working on some important project you suddenly face such an issue:

Firgure1. Oops!

Well, getting rid of this is easy, just follow the below-mentioned methods, and your issue will be fixed in a breeze!

Method #1: Change the <uses-sdk> line

As easy as it might sound, but changing the SDK really fixes this issue, and it might be the easiest one out there, simply do this,

<uses-sdk android:minSdkVersion="14" android:targetSdkVersion="16" />

and then change the minSDKVersion like this

android {
    compileSdkVersion 17
    buildToolsVersion "17.0.0"

    defaultConfig {
        minSdkVersion 14
        targetSdkVersion 16
    }
}

Note: Make sure that you edit your gradle.build on Android Studio case. Values are overridden during build!



Method #2: A missing, closing, or open tag

This method is not direct, it needs some sort of working on itself, as you will need to find if some tags in your Android Manifest are missing or not! Here’s an example if the <application> tag is not closed then close it like this:

</application>

Method #3: Error with the Google Play Services Framework

You may encounter this error if your app/project uses Google Play Services to deliver certain features to the end-user as Android 2.2 is required by the Google Play Services, which is version 8 of SDK. Change your minSDK Version to be at least at 8 like the code sample below:

android {
    compileSdkVersion 17
    buildToolsVersion "17.0.0"

    defaultConfig {
        minSdkVersion 8
           // Change or Add this
        targetSdkVersion 16
    }
}

dependencies {
    // Other Dependencies Go here
    compile 'com.android.support:support-v4:13.0.+'
    compile 'com.google.android.gms:play-services:3.1.36'
}

Method #4: Multi-Module Project Error

If your Android Project has multiple modules or flavors then there could be errors due to that for that the best way out is trying to merge manifest files from all modules into the Main manifest, if you have a multi-module project using Android Studio, and Gradle. If you have module A and module B, and you declare some activity from module B in the A manifestation, the Gradle will find a problem during the combination. In manifest files, try to delete the cross-module reference.

Method #5: The allow-backup case

As the Android System evolves it gets through a variety of different features and some of them slay the project, one of them might be the allowBackup line in the Manifest, which could be triggering the error back and forth, making it false like the way given below might also help resolve this issue!

<application
    android:allowBackup="false"
    <1-- Make this false-->
    android:label="@string/app_name"
    android:supportsRtl="true">
</application>

Hope the above methods provide you with a possible resolution to the problem and you’re back at completing the waiting project!
May the Force be with you!

Want a more fast-paced & competitive environment to learn the fundamentals of Android?
Click here to head to a guide uniquely curated by our experts with the aim to make you industry ready in no time!
My Personal Notes arrow_drop_up
Recommended Articles
Page :