Manifest merger failed error

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?

Answers


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


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 :

  1. Product flavors and build types specific manifest files.
  2. Main manifest file for the application.
  3. 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".


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.


I fixed same issue. Solution for me:

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

Example here


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

  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

  1. There's no duplicacy like same permissions added in manifest file twice, same activity mention twice
  2. If you have delete any activity from your project, delete it from your manifest file as well
  3. 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


I just removed

android:label="@string/app_name

from the manifest file and it worked!


Need Your Help

Auto import not working for Android classes in Android studio

android-studio import android-sdk-tools

I am working on a project in Android studio. Suddenly, auto import stopped working in android studio for Android classes, like Android.widgets.Textview, etc. In my settings, auto import is enabled....

What does Redis do when it runs out of memory?

nosql redis

This might be easy question but I am having a hard time finding the answer. How does Redis 2.0 handle running out of maximum allocated memory? How does it decide which data to remove or which data to