Disable Manifest Merger in Android Gradle Build

by

Edit: this is actually possible though indirectly, starting with 0.3

What you need to do is disable the processManifest task so that it doesn’t run and tell the processResources where the manifest to use is:

android.applicationVariants.all { variant ->
    variant.processResources.manifestFile = file('src/main/AndroidManifest.xml')
    variant.processManifest.enabled=false
}

Note that if you are customizing the app package name through the DSL, you should keep the default manifest untouched in the default location to provide a consistent package name for the R classes, and then have your manually merged manifests somewhere else and point each variant processResources task to them.

More Related Contents:

  1. How to configure gradle to work “offline” (using cached dependencies)
  2. How to define different dependencies for different product flavors
  3. How to change the Android app package name when assembling with Gradle?
  4. Run task before compilation using Android Gradle plugin
  5. How to set different applicationId for each flavor combination using flavorDimensions?
  6. How to use the Renderscript Support Library with Gradle
  7. failed to find target with hash string android-23
  8. Automatic versioning of Android build using git describe with Gradle
  9. Android studio, gradle and NDK
  10. How to use opencv in using Gradle?
  11. Android Command line tools sdkmanager always shows: Warning: Could not create settings
  12. Why are there two build.gradle files in an Android Studio project?
  13. Couldn’t locate lint-gradle-api-26.1.2.jar for Flutter project
  14. Error – Android resource linking failed (AAPT2 27.0.3 Daemon #0)
  15. Error:Execution failed for task ‘:app:compileDebugKotlin’. > Compilation error. See log for more details
  16. Gradle failed to resolve library in Android Studio
  17. Publish an Android library to Maven with AAR and sources JAR
  18. Gradle Error:Execution failed for task ‘:app:processDebugGoogleServices’
  19. AndroidStudio – Module Dependencies in Gradle
  20. Running a specific instrumentation unit test with Gradle
  21. java.lang.NullPointerException (no error message)
  22. Gradle’s dependency cache may be corrupt (this sometimes occurs after a network connection timeout.)
  23. Android studio 3.2.1 ArtifactResolveException: Could not resolve all artifacts for configuration ‘:classpath’
  24. Travis CI failed because cannot accept license Constrain Layout
  25. Gradle project sync failing after Google announced the new sdk versioning system
  26. Gradle: How to Build different flavours of different built types?
  27. Gradle warning: variant.getOutputFile() and variant.setOutputFile() are deprecated
  28. Android-Studio : Error: Could not create the Java Virtual Machine
  29. How to import RecyclerView for Android L-preview
  30. Gradle failed to build when proguard is activated

Leave a Comment