I would like to apply some plugin per build type, something like: build.gradle: android{ .... buildTypes{ release{ .... apply plugin: 'io.fabric' } debug{ .... apply plugin: 'testfairy' } } ... } But …

Well, these are some uses cases: 1)These plugins are for crash reporting, so I don’t need them to be applied all the time (ex: I don’t need them for my daily local builds because I’m not going to track the crash on those builds, they are for development propose, no for sharing or tracking the crash…

A plugin really is a project-scoped concept. A project either has it or not. But the plugin should allow you to configure it at a finer grained level. For instance, the crash reporting plugin you mentioned should allow you to specify which buildTypes it should apply to. I guess it would be best to …

I realize this is an old issue, but I have a related issue: I want to apply a plugin at a different point of the file based on the product flavor. So I have something like this: android { compileSdkVersion 25 targetSdkVersion 25 ... productFlavors { legacy { minSdkVers…

Please get in touch with the maintainers of that plugin to sort out why you are getting that error. My explanation above applies to your case as well.

In case anybody else stumbles across this post, I was able to resolve the problem with a lot of persistence and a little bit of magic. It should be noted that I was following this guide . Instead of having two separate dependencies: dependencies { ... legacyCompile 'com.google.android.gms:…

The snippet above is just overriding a global variable, so you are now always using firebase 10.0.1 What you had before looks right, so please get in touch with the Android community to see why it is not working.

Plug-ins may be a project-level concept, but why? Downloading application of the plug-in based on build type to the plug-in itself doesn’t make any sense considering that Gradle itself is a build configuration tool . What is the reasoning against letting build.gradle decide when plug-ins are appli…

I dare to remind that we, as customers, do not have a goal of “having a high level concept” but rather to have “a good working solution”. A specific plugin it not an abstract entity, it has a semantic meaning. And as we already have an instrument to declare different semantic buckets - like flavours…

How to apply plugin based on build type (Android)

Help/Discuss

st_oehme (Stefan Oehme) March 18, 2016, 8:35pm 2

Plugins can’t be applied to only “part of your project”. They are either applied or not. What is the use case where this becomes a problem for you?

Topic		Replies	Views
How to apply a plugin only for certain build variant in Android? Help/Discuss	0	397	June 8, 2023
Apply plugin with version catalog Help/Discuss	1	4148	May 31, 2022
Apply plugin inside a plugin Help/Discuss plugins	21	13967	February 20, 2024
Android Root Project to Custom Gradle Plugin Help/Discuss	10	2239	April 16, 2023
Add configuration when plugin is applied, handling different plugin versions Help/Discuss	18	1472	September 29, 2023

How to apply plugin based on build type (Android)

Related topics