Why does my Android build fail with a "Manifest merger failed" error after adding the Pushwoosh SDK?

A "Manifest merger failed" error during an Android build usually means there are conflicts or inconsistencies in your AndroidManifest.xml file, often arising when merging manifests from different libraries like the Pushwoosh SDK.

Here are common causes and solutions:

1. Duplicate Permissions: Check if permissions required by Pushwoosh (e.g., INTERNET, ACCESS_NETWORK_STATE) are declared more than once. Remove any duplicate <uses-permission> tags from your app's main AndroidManifest.xml file.
2. Incompatible minSdkVersion: Ensure the minSdkVersion specified in your app-level build.gradle file meets the minimum requirement for the Pushwoosh SDK version you are using. Refer to the Pushwoosh Android SDK documentation for the current minimum required version (a previous support interaction suggested version 23 or higher might be needed, but always check the latest docs).
3. Other Conflicts: Use Android Studio's "Merged Manifest" view (found at the bottom of the manifest editor) to inspect the final combined manifest. This view highlights conflicts related to activities, services, providers, or other elements that couldn't be merged automatically. Resolve these conflicts based on Android's manifest merge rules.

If you continue to experience issues after checking these points, running your build with the --info or --debug flag (e.g., ./gradlew assembleDebug --info) can provide more detailed logs to help pinpoint the exact conflict.