Explicit android:exported Declaration Requirement in Android 12 and Solutions

Background and Android 12 Requirements

With the release of Android 12, Google introduced new security requirements: all Activity, Service, Receiver, and Provider components containing intent filters must explicitly declare the android:exported attribute. This change aims to enhance application security by preventing unauthorized component access.

Error Location Methods

When encountering the "Manifest merger failed with multiple errors" issue, the first step is to accurately identify the specific components missing exported declarations. Here are two effective troubleshooting approaches:

Method 1: Inspect Merged Manifest

Use Android Studio's Merged Manifest feature to visually examine the final merged manifest file:

1. Temporarily set targetSdkVersion to 30 to bypass Android 12 validation
2. Open the project's AndroidManifest.xml file
3. Click on the "Merged Manifest" tab at the bottom
4. Search for all component definitions missing the android:exported attribute
5. Restore the original targetSdkVersion setting

Method 2: Analyze Build Logs

Obtain detailed error information through Gradle build commands:

./gradlew assembleDebug --stacktrace --info | tee build_logs.txt

Search for keywords in the generated log file: activity#, service#, receiver#, provider# to find specific component location information.

Solution Approaches

Different repair strategies are employed based on the source of the components:

Own Code Component Fix

For components defined within the project itself, directly add the android:exported attribute in the manifest file:

<receiver
    android:name=".services.EventReceiver"
    android:exported="false"
    tools:node="merge" />

Third-party Library Component Override

For components from third-party libraries, override configuration is required in the main manifest file:

<provider
    android:name="com.example.ThirdPartyProvider"
    android:exported="false"
    tools:node="merge"
    tools:overrideLibrary="com.example.library" />

Best Practices and Considerations

When setting the android:exported attribute, follow the principle of least privilege:

• Set to true only when the component needs to be accessed by other applications
• Always set to false for internally used components
• Must be explicitly declared for components containing intent filters
• Use tools:node="merge" to ensure proper attribute merging into the final manifest

Compatibility Considerations

Although Android 12 mandates explicit declaration, it's recommended to explicitly set the android:exported attribute in projects targeting all API levels to improve code readability and maintainability. For projects requiring backward compatibility, conditional configuration can handle behavioral differences across API levels.