Manifest Merger failed with multiple errors in Android Studio

So, I am a beginner into Android and Java. I just began learning. While I was experimenting with Intent today, I incurred an error.

Error:Execution failed for task ':app:processDebugManifest'. > Manifest merger failed with multiple errors, see logs 

I found some solutions here and tried to implement them, but it did not work.

This is my build.gradle :

apply plugin: 'com.android.application' android { compileSdkVersion 23 buildToolsVersion "23.0.0" defaultConfig { applicationId "com.example.rohan.petadoptionthing" minSdkVersion 10 targetSdkVersion 23 versionCode 1 versionName "1.0" } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } } } dependencies { compile fileTree(dir: 'libs', include: ['*.jar']) compile 'com.android.support:appcompat-v7:23.0.0' } 

This is my AndroidManifest :

<?xml version="1.0" encoding="utf-8"?> 

package="com.example.rohan.petadoptionthing" > <application android:allowBackup="true" android:icon="@mipmap/ic_launcher" android:label="@string/app_name" android:theme="@style/AppTheme" > <activity android:name=".MainActivity" android:label="@string/app_name" > <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity> <activity android:name=".Second" /> <activity android:name=".third"/> <activity android:name=".MainActivity"/> </application> 

This is my first week with coding, I am sorry if this is a really silly thing. I am really new to this and did not find any other place to ask. Sorry if I broke any rules

43 Answers

1 2 Next

Open application manifest (AndroidManifest.xml) and click on Merged Manifest tab on bottom of your edit pane. Check the image below:

From image you can see Error in the right column, try to solve the error. It may help some one with the same problem. Read more here.

Also, once you found the error and if you get that error from external library that you are using, You have to let compiler to ignore the attribute from the external library. //add this attribute in application tag in the manifest

 tools:replace="android:allowBackup" //Add this in the manifest tag at the top xmlns:tools="" 

Remove <activity android:name=".MainActivity"/> from your mainfest file. As you have already defined it as:

 <activity android:name=".MainActivity" android:label="@string/app_name" > <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity> 

So, Manifest file showing ambiguity.

I was also facing same issues, and after lot of research found the solution:

1. Your min sdk version should be same as of the modules you are using eg: your module min sdk version is 14 and your app min sdk version is 9 It should be same.
2. If build version of your app and modules not same. Again it should same ** In short, your app build.gradle file and manifest should have same configurations**
3. There's no duplicacy like same permissions added in manifest file twice, same activity mention twice.
4. If you have delete any activity from your project, delete it from your manifest file as well.
5. Sometimes its because of label, icon etc tag of manifest file:

a) Add the xmlns:tools line in the manifest tag.

b) Add tools:replace= or tools:ignore= in the application tag.

Example:

<manifest xmlns:android="" package="com.slinfy.ikharelimiteduk" xmlns:tools="" android:versionCode="1" android:versionName="1.0" > <application tools:replace="icon, label" android:label="myApp" android:name="com.example.MyApplication" android:allowBackup="true" android:hardwareAccelerated="false" android:icon="@drawable/ic_launcher" android:theme="@style/Theme.AppCompat" > </application> </manifest> 

6. If two dependencies are of not same version example: you are using dependency for appcompat v7:26.0.0 and for facebook com.facebook.android:facebook-android-sdk:[4,5) facebook uses cardview of version com.android.support:cardview-v7:25.3.1 and appcompat v7:26.0.0 uses cardview of version v7:26.0.0, So there is discripancy in two libraries and thus give error

Error:Execution failed for task ':app:processDebugManifest'.

Manifest merger failed : Attribute meta-data#android.support.VERSION@value value=(26.0.0-alpha1) from [com.android.support:appcompat-v7:26.0.0-alpha1] AndroidManifest.xml:27:9-38 is also present at [com.android.support:cardview-v7:25.3.1] AndroidManifest.xml:24:9-31 value=(25.3.1). Suggestion: add 'tools:replace="android:value"' to element at AndroidManifest.xml:25:5-27:41 to override.

So by using appcompat of version 25.3.1, We can avoid this error

By considering above points in mind, you will get rid of this irritating issue. You can check my blog too

For me THIS works -

Finding Merging Errors in AndroidManifest.xml

Click on Merged Manifest in AndroidManifest.xml

You can view manifest merging error in right column. It may help to solve this problem.

In addition to available solutions, please check this also.
If you have set android:allowBackup="false" in your AndroidManifest.xml then there may be a conflict for android:allowBackup="true" in other dependencies.

Solution
As suggested by @CLIFFORD P Y, switch to Merged Manifest in your AndroidManifest.xml. Android Studio will suggest to add tools:replace="android:allowBackup" in <application /> in your AndroidManifest.xml.

I was facing the same problem and I've just added one line in my manifest.xml and it worked for me.

tools:replace="android:allowBackup,icon,theme,label,name"> 

add this line under

<application android:name=".MyApplication" android:allowBackup="true" android:icon="@drawable/launcher" android:label="@string/app_name" android:largeHeap="true" android:screenOrientation="portrait" android:supportsRtl="true" android:theme="@style/AppThemecustom" tools:replace="android:allowBackup,icon,theme,label"> 

Hope it will help.

Just add below code in your project Manifest application tag...

<application tools:node="replace"> 

If your project targeted Android 12 then Add this in all <activity> tags with <intent-filter>

android:exported="true/false" 

I solved this with Refactor -> Migrate to AndroidX

GL

In my case it was showing an error because there was a redundancy in <uses-permission> element. So, please check in your AndroidManifest.xml file for the same.

Android Studio version is 3.0.1

Operating System is Windows 7

Here is the screenshot for reference.

Usually occurs when you have errors in your manifest.Open AndroidManifest.xml .Click on the merged manifest tab.The errors can be seen there .Also include suggestions mentioned there.When I had a similar problem while importing com.google.android.gms.maps.model.LatLng ,it suggested me to include tools:overrideLibrary="com.google.android.gms.maps" in the application tag and the build was successful.

My case i have fixed it by

build.gradle(Module:app)

defaultConfig { ---------- multiDexEnabled true } dependencies { ........... implementation 'com.google.android.gms:play-services-gcm:11.0.2' implementation 'com.onesignal:OneSignal:3.+@aar' } 

This answer releted to OnSignal push notification

If after you add a Android Library Module and you get this error.
You can fix it by simple remove the android:label="@string/app_name" from the AndroidManifest.xml of your Android Library Module

1. In AndroidManifest.xml:

   • At application, add tools:replace="android:icon, android:theme and
   • At the Manifest root, add xmlns:tools="

2. In build.gradle:

   • At root, add useOldManifestMerger true

The minium sdk version should be same as of the modules/lib you are using For example: Your module min sdk version is 26 and your app min sdk version is 21 It should be same.

I see the answers and they are complete and useful. Anyway, if you are completing the Jetpack Compose Testing codelab and you find this error in late 2021, the solution is not the accepted answer, you need to downgrade your target sdk version to 30.

In app/build.gradle, replace:

targetSdkVersion 31 

with:

targetSdkVersion 30 

And run the Android Tests again

I was also facing this error. In the build log the last line was "Failed to compile values file".

So if you're facing the same issue, then just adding the following line in the gradle.properties file will most probably fix the issue.

android.enableJetifier=true 

I mean it fixed Manifest Merger failed with multiple errors in Android Studio error for me.

solution for me was like this:

1- open manifest

2-On top right , check highlighted problems like below:

3-click on problems icon in red. this will open problems tab like below.

4- solve them one by one

for the past few days I was also going through the same issue. But after, a lot of research I finally found a solution for this.
In order to solve this issue, what you need to do is:
1. Check if your project's build.gradle file and the module's build.gradle file contain same versions of all dependencies.
2. Make sure, your project's compileSdkVersion, buildToolsVersion, minSdkVersion and targetSdkVersion matches the one in the modules or libraries that you have added into the project.

compileSdkVersion 25 buildToolsVersion "25.0.0" defaultConfig { applicationId "com.example.appname" minSdkVersion 16 targetSdkVersion 25 versionCode 22 versionName "2.0.3" } 

Hope, this helps.

Open your gradle console, then you see gradle suggest you to add the particular line (Like: tools:replace="android:allowBackup" or tools:replace="android:label" etc). Add that line into your manifest file under tag and sync gradle, that's it.

In my case it happened for leaving some empty intent-filter inside the Activity tag

 <activity android:name=".MainActivity" android:label="@string/app_name" android:theme="@style/AppTheme.NoActionBar"> <intent-filter> </intent-filter> </activity> 

So just removing them solved the problem.

 <activity android:name=".MainActivity" android:label="@string/app_name" android:theme="@style/AppTheme.NoActionBar"> </activity> 

The following hack works:

1. Add the xmlns:tools="" line in the manifest tag
2. Add tools:replace="android:icon,android:theme,android:allowBackup,label,name" in the application tag

I was using the FirebaseUI Library along with the Facebook SDK Library, which was causing me the issue.

implementation 'com.firebaseui:firebase-ui-database:0.4.4' implementation 'com.facebook.android:facebook-android-sdk:[4,5)' 

And from [here][1], I got rid of this issue.

With the latest update of FirebaseUI library, previous version of Facebook SDK is also a part of it.

If you are using the both the libraries, please remove the Facebook SDK Library.

UPDATE

From the Android Studio 3.0 and the later versions, app.gradle file is required to use implementation or api instead of compile for adding the dependencies to the app.

This error occurs because you don't have proper statements at the Manifest root such:

<manifest xmlns:android="" xmlns:tools="" package="com.example.test"> 

So you should remove additional texts in it.

In my case, I solved it by updating the classpath in build.gradle (Project) file to the latest version.

It was like this:

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

After updating to the latest version:

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

Everything worked fine! Hope this helps someone if all the above answers don't solve the issue.

As a newbie to Android Studio, in my case, I had moved an existing project from Eclipse to Android Studio and found that there was a duplicate definition of an activity within my Manifest.xml that hadn't been picked up by Eclipse was shown as a Gradle error.

I found this by going to the Gradle Console (bottom right of the screen).

Happened with me twice when I refractor (Rename with SHIFT + F6) the name of a field in our files and it asks you to change it everywhere and we without paying attention change the name everywhere. For example, if you have a variable name "id" in your Java class and you rename it with SHIFT + F6. If you don't pay attention to the next dialog which will ask you wherever else it is going to change the id and you tick check all it will change all the id in your layout files from the new value.

this is very simple error only occur when you define any activity call two time in mainifest.xml file Example like

<activity android:name="com.futuretech.mpboardexam.Game" ></activity> //and launcher also------like that //solution:use only one 

Put this at the end of your app module build.gradle:

configurations.all { resolutionStrategy.eachDependency { DependencyResolveDetails details -> def requested = details.requested if (requested.group == 'com.android.support') { if (!requested.name.startsWith("multidex")) { details.useVersion '25.3.0' } } }} 

from this

Supplement the answer Phan Van Linh. I deleted these lines:

 android:icon="@mipmap/ic_launcher" android:label="name" 

1 2 Next