如何将单个Flavor下的复杂AndroidManifest.xml拆分为多个文件？

Absolutely, you can split your unwieldy AndroidManifest.xml into focused, maintainable files—even for a single app flavor. Here's a step-by-step guide using Android Gradle's built-in manifest merging, which works perfectly for this scenario even if the official docs don't explicitly call it out.

We’ll structure your manifests by functionality, just as you requested:

Step 1: Create Split Manifest Files #

Each file will hold a specific category of declarations. All files need a root <manifest> tag, but you can reuse your app’s package name (or omit it—Gradle will inherit the main manifest’s package).

AndroidManifest_general.xml (Global Config) #

Store permissions, app-level meta-data, SDK requirements, or feature declarations:

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

    <uses-sdk android:minSdkVersion="21" android:targetSdkVersion="34" />
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

    <application>
        <meta-data
            android:name="com.google.android.gms.version"
            android:value="@integer/google_play_services_version" />
    </application>
</manifest>

AndroidManifest_content.xml (UI Components) #

Keep all Activities, Services, and Content Providers here:

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.your.app">

    <application>
        <activity android:name=".ui.MainActivity">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
        <activity android:name=".ui.DetailActivity" />
        <service android:name=".data.sync.SyncService" />
    </application>
</manifest>

AndroidManifest_widgets.xml (Widget Declarations) #

Hold AppWidget Providers and their related resources:

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.your.app">

    <application>
        <receiver android:name=".widget.MyAppWidget">
            <intent-filter>
                <action android:name="android.appwidget.action.APPWIDGET_UPDATE" />
            </intent-filter>
            <meta-data
                android:name="android.appwidget.provider"
                android:resource="@xml/my_app_widget_info" />
        </receiver>
    </application>
</manifest>

Step 2: Configure Gradle to Merge Files #

The manifest.srcFile property only accepts one main file, but you can use manifest.from to add additional manifests. Modify your module-level build.gradle (or build.gradle.kts):

Groovy DSL #

android {
    sourceSets {
        main {
            // Main manifest: Keep core app config (package, icon, theme, application class)
            manifest.srcFile 'src/main/AndroidManifest.xml'
            // Add your split manifests to the merge list
            manifest.from 'src/main/AndroidManifest_general.xml',
                          'src/main/AndroidManifest_content.xml',
                          'src/main/AndroidManifest_widgets.xml'
        }
    }
}

Kotlin DSL #

android {
    sourceSets {
        main {
            manifest.srcFile(file("src/main/AndroidManifest.xml"))
            manifest.from(
                file("src/main/AndroidManifest_general.xml"),
                file("src/main/AndroidManifest_content.xml"),
                file("src/main/AndroidManifest_widgets.xml")
            )
        }
    }
}

Your main AndroidManifest.xml can be minimal, just holding essential app-level settings:

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.your.app">

    <application
        android:name=".MyApplication"
        android:icon="@mipmap/ic_launcher"
        android:theme="@style/AppTheme">
        <!-- Components will merge automatically from split files -->
    </application>
</manifest>

Step 3: Resolve Merging Conflicts #

If multiple manifests declare the same element (e.g., duplicate meta-data), use the tools:node attribute to define resolution behavior:

• tools:node="merge": Combine attributes (default for most cases)
• tools:node="replace": Use this element instead of others with the same name
• tools:node="remove": Delete the element from the merged manifest

Example of replacing a conflicting meta-data entry:

<meta-data
    android:name="com.your.app.custom_config"
    android:value="updated_value"
    tools:node="replace" />

Step 4: Verify the Merged Result #

Open your main manifest in Android Studio and switch to the Merged Manifest tab (bottom of the editor). This shows the final combined manifest, with annotations indicating which source each element came from—perfect for debugging.

Bonus Tips #

• Add more split files (e.g., AndroidManifest_notifications.xml for broadcast receivers) by extending the manifest.from list.
• Keep each manifest focused on one functionality to simplify maintenance.
• The merging engine works identically to library/flavor merging—this is a fully supported, official workflow.

内容的提问来源于stack exchange，提问作者Sergey Krivenkov