Android build errorAndroid: “Manifest merger failed”

Why the manifests don’t merge, and the fix

1. 01

   android:exported is missing (Android 12 and higher)

   “Manifest merger failed : Apps targeting Android 12 and higher are required to specify an explicit value for android:exported when the corresponding component has an intent filter defined.” Android Developers, Behavior changes: Apps targeting Android 12

   When an app targets Android 12 or higher, every activity, service or broadcast receiver with an intent filter must say whether other apps can start it. Flutter and React Native apps often hit this after raising targetSdk. Set it in your own manifest, and update plugins whose manifests are missing it.

   <activity
       android:name=".MainActivity"
       android:exported="true">
       <intent-filter>
           <action android:name="android.intent.action.MAIN" />
           <category android:name="android.intent.category.LAUNCHER" />
       </intent-filter>
   </activity>

2. 02

   Which value to use

   “If the app component includes the LAUNCHER category, set android:exported to true. In most other cases, set android:exported to false.” Android Developers, Behavior changes: Apps targeting Android 12

   The activity that opens from the home screen needs true. Most other components should be false unless another app is meant to start them, such as a share target or a deep link handler.

3. 03

   Two manifests set the same attribute differently

   “If any conflicts occur, they appear under Merging Errors with a recommendation for how to resolve the conflict using merge rule markers.” Android Developers, Manage manifest files

   A library may set android:label, android:theme, android:allowBackup or another attribute to a different value than your app. Open the Merged Manifest tab to see the clash, then mark the attribute in your manifest with tools:replace so your value wins.

   <manifest xmlns:android="http://schemas.android.com/apk/res/android"
       xmlns:tools="http://schemas.android.com/tools">
       <application
           android:allowBackup="false"
           tools:replace="android:allowBackup">
           <!-- your activities -->
       </application>
   </manifest>

4. 04

   A library needs a higher minSdk

   “By default, when importing a library with a minSdk value that's higher than the main manifest file, an error occurs and the library cannot be imported.” Android Developers, Manage manifest files

   If a library declares a higher minSdk than your app, the merge fails, naming both versions. The safe fix is to raise minSdk in the app module’s build.gradle to match. tools:overrideLibrary on the uses-sdk tag skips the check, but the library may then crash on older devices, so only use it when you know the code path is guarded.

   // app/build.gradle: the usual fix
   android {
       defaultConfig {
           minSdk 23 // match the version named in the error
       }
   }
   
   <!-- last resort, in AndroidManifest.xml -->
   <uses-sdk tools:overrideLibrary="com.example.lib" />

Checked against the vendor’s docs on November 7, 2026: Android Developers: Manage manifest files (merging, conflicts, tools:replace); Android Developers: Behavior changes for apps targeting Android 12 (android:exported).

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

• from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
• from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start

Related: Flutter Gradle task assembleDebug failed · Google Play target API level requirement · Android cleartext HTTP blocked