Android Studio error: “Manifest merger failed: Apps targeting Android 12”

We Are Going To Discuss About Android Studio error: “Manifest merger failed: Apps targeting Android 12”. So lets Start this Java Article.

Android Studio error: “Manifest merger failed: Apps targeting Android 12”

  1. Android Studio error: “Manifest merger failed: Apps targeting Android 12”

    You need to specify android:exported="false" or android:exported="true"

  2. Manifest merger failed: Apps targeting Android 12

    You need to specify android:exported="false" or android:exported="true"

Solution 1

You need to specify android:exported="false" or android:exported="true"


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

as mentioned in the document:

If your app targets Android 12 and contains activities, services, or
broadcast receivers that use intent filters, you must explicitly
declare the android: exported attribute for these app components.

Warning: If an activity, service, or broadcast receiver uses intent
filters and doesn’t have an explicitly-declared value for
android:exported, your app can’t be installed on a device that runs
Android 12.

Also check when to use true/false for the ‘android:exported’ value.

Original Author Mittal Varsani Of This Content

Solution 2

In your manifest, add android:exported=”true” or android:exported=”false ” in your default launching activity attribute.

Done! You are all right to run your apps on Android 12.

<manifest ... >

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

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

Set the android:exported value according to your requirement.

Whether the broadcast receiver can receive messages from non-system sources outside its application — “true” if it can, and “false” if not. If “false”, the only messages the broadcast receiver can receive are those sent by the system, components of the same application, or applications with the same user ID.

If unspecified, the default value depends on whether the broadcast receiver contains intent filters. If the receiver contains at least one intent filter, then the default value is “true”. Otherwise, the default value is “false”.

This attribute is not the only way to limit a broadcast receiver’s external exposure. You can also use permission to limit the external entities that can send messages (see the permission attribute).

From Android Documentation

Original Author Shihab Uddin Of This Content

Solution 3

If you didn’t find in your manifest the place where there is an activity without the tag “android: exported = false” then it’s likely that it is in your dependencies… in order to pinpoint where exactly, first downgrade “compileSdkVersion” to 30 and “targetSdkVersion” to 30 so it builds.

android {
    buildToolsVersion "30.0.3"

    defaultConfig {
        minSdkVersion 23

After that, in the main manifest.xml window there is a tab with “merged manifest”. There you can inspect what activity exactly didn’t have the “android: exported = false” attribute.

In my case it was because of third-party tools:

build.gradle (: app):

debugImplementation 'com.squareup.leakcanary:leakcanary-android:2.7'
debugImplementation "com.github.markzhai:blockcanary-android:1.5.0"
releaseImplementation "com.github.markzhai:blockcanary-no-op:1.5.0"

Also, for services I had to add the attribute:




As my problem was in a third-party dependency and it’s not going to be updated soon, I just added a <activity> declaration with the flag android:exported=”true” and exported=”false” where needed to override the initial declaration, also as I need this dependency in Debug only I added a new AndroidManifest.xml file in src/debug:

For leak_canary:

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

<manifest xmlns:android="">


            <intent-filter android:label="@string/leak_canary_import_hprof_file">

                <action android:name="android.intent.action.VIEW" />

                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />

                <data android:scheme="file" />
                <data android:scheme="content" />
                <data android:mimeType="*/*" />
                <data android:host="*" />

                <data android:pathPattern=".*\\.hprof" />
                <data android:pathPattern=".*\\..*\\.hprof" />
                <data android:pathPattern=".*\\..*\\..*\\.hprof" />
                <data android:pathPattern=".*\\..*\\..*\\..*\\.hprof" />
                <data android:pathPattern=".*\\..*\\..*\\..*\\..*\\.hprof" />
                <data android:pathPattern=".*\\..*\\..*\\..*\\..*\\..*\\.hprof" />
                <data android:pathPattern=".*\\..*\\..*\\..*\\..*\\..*\\..*\\.hprof" />

            android:theme="@style/leak_canary_Theme.Transparent" />

            android:exported="false" />


You might as well just use the tools:node=”merge” attribute and declare the android:exported=true|false as LeoFarage kindly suggested.

Original Author Xavier Vega Of This Content

Solution 4

I ran into the same issue after targeting Android 12 in my project.

The problem was the project was quite big, with multiple AndroidManifest.xml files, and android:exported missing in many places.

I ended up creating a Gradle task to fill the missing android:exported attributes automatically for me.

Here is the link.

Original Author Dat Pham Tat Of This Content


So This is all About This Tutorial. Hope This Tutorial Helped You. Thank You.

Also Read,


I am an Information Technology Engineer. I have Completed my MCA And I have 4 Year Plus Experience, I am a web developer with knowledge of multiple back-end platforms Like PHP, Node.js, Python and frontend JavaScript frameworks Like Angular, React, and Vue.

Leave a Comment