Manifest Merger failed with multiple errors in Android Studio


Android Problem Overview

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: ''

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'), ''

dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
compile ''

This is my AndroidManifest :

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

package="com.example.rohan.petadoptionthing" >


    android:theme="@style/AppTheme" >
        android:label="@string/app_name" >
            <action android:name="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />

    <activity android:name=".Second"

    <activity android:name=".third"/>
    <activity android:name=".MainActivity"/>


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

Android Solutions

Solution 1 - Android

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

enter image description here

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

   //Add this in the manifest tag at the top


Solution 2 - Android

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

        android:label="@string/app_name" >
            <action android:name="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />

So, Manifest file showing ambiguity.

Solution 3 - Android

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.


<manifest xmlns:android=""
    android:versionName="1.0" >
      tools:replace="icon, label"
      android:theme="@style/Theme.AppCompat" >


>6. If two dependencies are of not same version example: you are using dependency for appcompat v7:26.0.0 and for facebook[4,5) facebook uses cardview of version 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 value=(26.0.0-alpha1) from [] AndroidManifest.xml:27:9-38 is also present at [] 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

Solution 4 - Android

For me THIS works -

Finding Merging Errors in AndroidManifest.xml

enter image description here

Click on Merged Manifest in AndroidManifest.xml

enter image description here

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

Solution 5 - Android

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.

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.

Solution 6 - Android

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


> add this line under


Hope it will help.

Solution 7 - Android

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


Solution 8 - Android

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


Solution 9 - Android

I solved this with Refactor -> Migrate to AndroidX


Solution 10 - Android

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.

Screen-shot which shows redundancy in manifest file.

Solution 11 - Android

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 ,it suggested me to include tools:overrideLibrary="" in the application tag and the build was successful.

Solution 12 - Android

My case i have fixed it by

> build.gradle(Module:app)

defaultConfig {
multiDexEnabled true
dependencies {
    implementation ''
    implementation 'com.onesignal:OneSignal:3.+@aar'

This answer releted to OnSignal push notification

Solution 13 - Android

  1. In AndroidManifest.xml:
  • At application, add tools:replace="android:icon, android:theme and
  • At the Manifest root, add xmlns:tools="
  1. In build.gradle:
  • At root, add useOldManifestMerger true

Solution 14 - Android

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

Solution 15 - Android

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.

Solution 16 - Android

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


targetSdkVersion 30

And run the Android Tests again

Solution 17 - Android

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 file will most probably fix the issue.


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

Solution 18 - Android

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. problems tab

4- solve them one by one

Solution 19 - Android

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.

Solution 20 - Android

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 '[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.


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.

Solution 21 - Android

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.

Solution 22 - Android

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





So just removing them solved the problem.


Solution 23 - Android

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

Solution 24 - Android

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

<manifest xmlns:android=""

So you should remove additional texts in it.

Solution 25 - Android

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 ''

After updating to the latest version:

dependencies {
    classpath ''

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

Solution 26 - Android

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).

Solution 27 - Android

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.

Solution 28 - Android

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 

Solution 29 - Android

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

configurations.all {
resolutionStrategy.eachDependency { DependencyResolveDetails details ->
    def requested = details.requested
    if ( == '') {
        if (!"multidex")) {
            details.useVersion '25.3.0'

from this

Solution 30 - Android

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


Solution 31 - Android

i sloved this problem by removing below line from AndroidManifest.xml


Solution 32 - Android

Just migrate to Androidx as shown above and then set teh minimum sdk version to 26...with no doubts this works perfectly

Solution 33 - Android

In my case i was using some annotations from jetbrains library. I removed those annotations and dependencies and it worked fine.

So please check the libraries in android code and dependencies carefully.

Solution 34 - Android

If you're using multiple manifestPlaceholder items in your build.gradle file, you must add them as array elements, instead of separate items.

For example, this will cause a build error or compile error: "java.lang.RuntimeException: Manifest merger failed with multiple errors":

android {
    defaultConfig {
        manifestPlaceholders = [myKey1: "myValue1"]
        manifestPlaceholders = [myKey2: "myValue2"] // Error!

This will fix the error:

android {
    defaultConfig {
        manifestPlaceholders = [myKey1: "myValue1", myKey2: "myValue2"]

Solution 35 - Android

This is because you are using the new Material library with the legacy Support Library.

You have to migrate to androidx in order to use

If you are using android studio v 3.2 or above, simply

> go to refactor ---> MIGRATE TO ANDROID X.

Do make a backup of your project.

Solution 36 - Android

After seeing CLIFFORD's answer to see the error, what helped me to solve this issue was renaming 'android:namex' to 'android:name' in the intent-filter action tag. In case if the same solution helps someone else .

    <activity android:name=".MainActivity">
            <action android:namex="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />

Solution 37 - Android

I had a weird encounter with this problem. when renaming variable name to user_name, I mistakenly rename all of the name to user_name for the project. So my xml tag <color name:""> became <color user_name:""> same goes for string, style, manifest too. But when I check merged manifest, it showed nothing, because I had only one manifest, nothing to find.

So, check if you have any malformed xml file or not.

Solution 38 - Android

In my case my application tag includes:


I resolved this issue my adding new param as android:appComponentFactory=""

So my final application tag becomes:


I encountered above issue when I tired using firebase-auth latest version as "19.3.1". Whereas in my project I was already using firebase but version was "16.0.6".

Solution 39 - Android

check if you've any duplicate activity declared in the manifest. That was my mistake for this error and problem solved, after deleting the duplicate.

Solution 40 - Android

For all of you that have the same problem but when you merge the manifest and there's no error at all this solution worked for me without edit your "Manifest" file and changed any configuration, delete this, delete that ect.

  1. Open your "settings.gradle" file.
  2. Add this code "gradlePluginPortal()".
  • If your start a new project the code automatically might be there if you are using the updated Android Studio but you need to add once more, like code below:

      pluginManagement {
      repositories {
          maven {url ''}

and put the code "gridlePluginCentral()" once more.

dependencyResolutionManagement {
    repositories {
        maven {url ''}

In my case problems like this happened usually when we use the github user libraries and used it for layout files or as "imports" in java files. It's always a good idea to keep your Android Studio up-to-date and leave the old version as there are usually changes to configuration, libraries and other supporting files. And it's best to avoid using libraries from github users, preferably using libraries from Google.

Solution 41 - Android

in my case I was using multi models on firebase vision Dependencies in manifest file's meta-data tag, so I mixed them in one value parameter and it did solve my is how :


Solution 42 - Android

Simple Answer Cross Check :

You might be defined Same Activity multiple times in the manifest.xml file.


Activity or service or receiver you have defined in the manifest.xml file which is not in your project structure.

Solution 43 - Android

I solved this by removing android:replace tag


All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionRohanView Question on Stackoverflow
Solution 1 - AndroidCLIFFORD P YView Answer on Stackoverflow
Solution 2 - AndroidAndroid GeekView Answer on Stackoverflow
Solution 3 - AndroidKimmi DhingraView Answer on Stackoverflow
Solution 4 - AndroidA JView Answer on Stackoverflow
Solution 5 - AndroidChintan ShahView Answer on Stackoverflow
Solution 6 - AndroidPre_hackerView Answer on Stackoverflow
Solution 7 - AndroidsankalpView Answer on Stackoverflow
Solution 8 - AndroidAqifView Answer on Stackoverflow
Solution 9 - AndroidBraian CoronelView Answer on Stackoverflow
Solution 10 - AndroidParth PatelView Answer on Stackoverflow
Solution 11 - AndroidArchana PrabhuView Answer on Stackoverflow
Solution 12 - AndroidMd. ShofiullaView Answer on Stackoverflow
Solution 13 - Androidao wuView Answer on Stackoverflow
Solution 14 - AndroidLinhView Answer on Stackoverflow
Solution 15 - AndroidEjaz AhmadView Answer on Stackoverflow
Solution 16 - AndroidvoghDevView Answer on Stackoverflow
Solution 17 - AndroidBuckyView Answer on Stackoverflow
Solution 18 - Androidصلي علي محمد Atef FaroukView Answer on Stackoverflow
Solution 19 - AndroidRahul Deep SinghView Answer on Stackoverflow
Solution 20 - AndroidMohammedsalim ShivaniView Answer on Stackoverflow
Solution 21 - AndroidNazmus SaadatView Answer on Stackoverflow
Solution 22 - AndroidDr TJView Answer on Stackoverflow
Solution 23 - AndroidShoaib AhmedView Answer on Stackoverflow
Solution 24 - AndroidMohsen HrtView Answer on Stackoverflow
Solution 25 - AndroidRoyce ThomasView Answer on Stackoverflow
Solution 26 - AndroidJanBView Answer on Stackoverflow
Solution 27 - AndroidRakesh YadavView Answer on Stackoverflow
Solution 28 - AndroidExpert SuggestionView Answer on Stackoverflow
Solution 29 - AndroidSHADOW NETView Answer on Stackoverflow
Solution 30 - AndroidDenView Answer on Stackoverflow
Solution 31 - Androidsaigopi.meView Answer on Stackoverflow
Solution 32 - Androidsammy mutahiView Answer on Stackoverflow
Solution 33 - AndroidChaman GurjarView Answer on Stackoverflow
Solution 34 - AndroidMr-IDEView Answer on Stackoverflow
Solution 35 - AndroidFazal JarralView Answer on Stackoverflow
Solution 36 - AndroidFarhanView Answer on Stackoverflow
Solution 37 - Androidtouhid udoyView Answer on Stackoverflow
Solution 38 - AndroidNikhil LotkeView Answer on Stackoverflow
Solution 39 - AndroidKwesi WelbredView Answer on Stackoverflow
Solution 40 - AndroidJimiView Answer on Stackoverflow
Solution 41 - AndroidPayam KaramvandiView Answer on Stackoverflow
Solution 42 - AndroidAmbilpura Sunil KumarView Answer on Stackoverflow
Solution 43 - AndroidGurjap singhView Answer on Stackoverflow