Manifest merger failed error

Question

I am in the process of moving my current projects huge application into Android Studio and Gradle. I am currently stuck on the following issue:

Error:(87, 9) Execution failed for task ':App:processDebugManifest'.
> Manifest merger failed : Attribute application@label value=(@string/app_label) from AndroidManifest.xml:87:9
    is also present at ANDROID_APPLICATION:Library:unspecified:9:18 value=(@string/app_name)
    Suggestion: add 'tools:replace="android:label"' to <application> element at AndroidManifest.xml:82:5 to override

I have tried adding the following attributes to the main AndroidManifest.xml file:

tools:replace="android:label, *App Name*"
tools:replace="android:label, @string/app_label"
tools:replace="android:label"

None of these attribute definitions works. What am I doing wrong?

score 196 · Accepted Answer · edited Jan 26 '20 at 06:40

196

Give this a try:

Add this to <manifest/>

xmlns:tools="http://schemas.android.com/tools"

Add this to <application/>

tools:node="replace"

Based on this, it should override all the elements. "Replace the lower priority declaration with the annotated one."

edited Jan 26 '20 at 06:40

Neeraj

2,376
2
24
41

answered Jan 23 '15 at 09:32

Kayvan N

8,108
6
29
38

thanks a lot. for some reason `tools:replace` refuses to work, but this works (possibly a bit eagerly, though) – njzk2 Jul 03 '15 at 22:16
this is not working for me in AS 1.3.2 with gradle plugin 1.2.3 or 1.3.0 – dm78 Sep 25 '15 at 16:35
This issue is due to issue in Manifest file or build.gradle file. You can check my post https://wordpress.com/post/dhingrakimmi.wordpress.com/23 – Kimmi Dhingra Sep 10 '17 at 17:24
In my case string was missing – Pawan Chaurasiya Oct 25 '18 at 17:20
After app build successfully then immediately app crashed. – EDISON J Jan 02 '20 at 06:56
2

@kayvan after using(tools:node="replace") this i am getting crash in firebase setup – Mohd Qasim May 29 '20 at 06:33
is there any way to add this xmlns to android manifest from config.xml for ionic ? – Ragesh Pikalmunde Aug 14 '20 at 05:26
For the love of all that is holy DO NOT USE THIS IF YOU USE FIREBASE. I wasted 2 days trying to understand why my Firebase setup wasn't working, and finally traced it back to this. – Aron Jan 11 '21 at 01:15

score 41 · Answer 2 · answered Aug 03 '15 at 17:26

Background

When the manifest files are being merged, there is a conflict with the label attribute.

In general, there are three types of manifest files that need to be merged into a single resulting app manifest, here in priority order :

Product flavors and build types specific manifest files.
Main manifest file for the application.
Library manifest files.

Resolutions

The conflict can be resolved in one of two ways:-

Remove the conflicting label

Remove the conflicting attribute from the library (or lower-level) manifest file.

In this case, the ANDROID_APPLICATION:Library:unspecified:9:18 value=(@string/app_name) has a @string/app_name value defined that's different from that in the main application. So if it's not required, then remove it -- simply remove the android:label="@string/app_name" from the library file's AndroidManifest.xml file.

Add an attribute to allow an automatic resolution to the conflict

There are several special attribute markers (in the tools namespace) that may be used to express a specific decision for how to resolve conflicts.

In this case, to explicitly cause the main app's android:label to override any other (e.g. library file) application labels, add the xmlns:tools="http://schemas.android.com/tools" definition to the <manifest> node, and tools:replace="label" to the <application> node.

Here is an example - use this in the main application's AndroidManifest.xml file:

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

    <application
        android:label="@string/app_name"
        tools:replace="label"/>
</manifest>

This approach would also work with any other conflicting attributes; for example if the icon attribute was also in conflict, it could be changed to tools:replace="label, icon".

this is not working for me in AS 1.3.2 with gradle plugin 1.2.3 or 1.3.0 — dm78, Sep 25 '15 at 16:34
Is there any specific reason why android:label would be required/wanted in library's app manifest? — Blaž Šnuderl, Oct 12 '15 at 09:17
@BlažŠnuderl I haven't tried without this, as it is the basis of labels used (and presented to users) in Activities within an application. See: http://developer.android.com/guide/topics/manifest/application-element.html#label — CJBS, Oct 12 '15 at 20:57
why would manifest files even be merged? i started getting this error after a normal build, I hadn't even done anything aside from edit java source files! — Michael, Nov 15 '16 at 03:51
@Michael Did you inadvertently add a reference to another package/library that happened to have a definition of a label that's the same as an existing one? — CJBS, Nov 15 '16 at 16:51
I don't know... tracked it down and it turned out my manifest had the correct min version, but there was a gradle build file which did not (easy enough to fix) leading to the question of why the build ever worked at all. — Michael, Nov 15 '16 at 21:17

score 6 · Answer 3 · answered Sep 25 '15 at 20:37

If you were fortunate, as I was, you can manually fix the problem with a hacky work-around.

AAR files are just .zip files with an .aar extension. In my case, I unzipped the .aar, removed the offending android:label from the library's AndroidManifest.xml, and then rearchived the remaining files with a .aar extension and everything seems to work perfectly with the new .aar.

FYI, this appears to be a known bug in the android gradle plugin.

this worked for me. all other solutions didnt worked – Saman Sattari Apr 28 '16 at 17:24 — Saman Sattari, Apr 28 '16 at 17:24

score 4 · Answer 4 · edited May 23 '17 at 12:34

4

I fixed same issue. Solution for me:

add the xmlns:tools="http://schemas.android.com/tools" line in the manifest tag
add tools:replace=.. in the manifest tag
move android:label=... in the manifest tag

Example here

edited May 23 '17 at 12:34

Community

1
1

answered Oct 28 '16 at 13:31

stefan K

633
5
4

score 1 · Answer 5 · edited Nov 26 '18 at 12:23

1

I just removed

android:label="@string/app_name

from the manifest file and it worked!

edited Nov 26 '18 at 12:23

Agilanbu

2,747
2
28
33

answered Oct 23 '18 at 15:44

itzo

1,220
14
18

this is working but it also change the app display name. – Viren V Varasadiya Jan 27 '21 at 08:23

score 1 · Answer 6 · answered Oct 20 '20 at 15:10

I modified the manifest file from

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example">

    <application
        android:allowBackup="true"
        android:label="@string/app_name"
        android:supportsRtl="true">
        <activity android:name=".SomeActivity"/>
    </application>
</manifest>

To

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example"
    xmlns:tools="http://schemas.android.com/tools">

    <application
        android:allowBackup="true"
        android:label="@string/app_name"
        android:supportsRtl="true"
        tools:replace="android:label">
        <activity android:name=".SomeActivity"/>
    </application>
</manifest>

And now the android:label is replaced by the label from the parent application.

Kimmi Dhingra · Answer 7 · 2017-09-10T17:23:49.323

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

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.

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

There's no duplicacy like same permissions added in manifest file twice, same activity mention twice

If you have delete any activity from your project, delete it from your manifest file as well

Sometimes its becuase 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="http://schemas.android.com/apk/res/android"
package="com.slinfy.ikharelimiteduk"
xmlns:tools="http://schemas.android.com/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>

By considering these points in mind, you will get rid of this manifest merger failed issue Check my post: This issue is due to issue in Manifest file or build.gradle file. You can check my post https://wordpress.com/post/dhingrakimmi.wordpress.com/23

score 0 · Answer 8 · edited Sep 11 '21 at 05:53

0

Try adding android.useAndroidX=true and android.enableJetifier=true in gradle.properties file. It helped me to solve my problem.

edited Sep 11 '21 at 05:53

m4n0

29,823
27
76
89

answered Sep 11 '21 at 05:13

Ashutosh Kumar

1

score 0 · Answer 9 · answered Jan 19 '22 at 05:30

0

I came across the same problem. In my case android:label was empty in AndroidManifest.xml file. Then I changed it as below

android:label="@string/app_name

Maybe this simple solution will help someone. Thank you.

answered Jan 19 '22 at 05:30

SandaliTP

795
5
7

Manifest merger failed error

9 Answers9

Background

Resolutions

Remove the conflicting label

Add an attribute to allow an automatic resolution to the conflict

Linked

Related