IssueTracker

The androidx.baselineprofile plugin generates additional <flavor>NonMinifiedRelease and <flavor>BenchmarkRelease variants for each original variant that's non-debuggable (release).

Sometimes not all combinations of flavor + build type are needed so it makes sense to disable certain variants with the androidComponents.beforeVariants API.

For example, a project has defined 1 flavor dimension "environment" with 4 flavors:

• dev
• demo
• mock
• prod

By default this produces 8 variants:

• devDebug, devRelease
• demoDebug, demoRelease
• mockDebug, mockRelease
• prodDebug, prodRelease

We can disable 4 of the variants that are irrelevant:

beforeVariants {
    it.enable = it.name in listOf(
        "devDebug",
        "demoDebug",
        "mockDebug",
        "prodRelease",
    )
}

When baseline profile plugin is applied to the app module, before any variant filtering it adds the following variants:

• devNonMinifiedRelease
• devBenchmarkRelease
• demoNonMinifiedRelease
• demoBenchmarkRelease
• mockNonMinifiedRelease
• mockBenchmarkRelease
• prodNonMinifiedRelease
• prodBenchmarkRelease

Let's say I want to generate baseline profile and run benchmark with just the devRelease variant.

The generated devNonMinifiedRelease and devBenchmarkRelease should be enough. So I would still filter out devRelease.

I'm also able to filter out the generated <mock|demo>NonMinifiedRelease and <mock|demo>BenchmarkRelease variants as well as the original <mock|demo>Release.

Now I also want to filter out prodNonMinifiedRelease and prodBenchmarkRelease as I don't need to generate BP or run benchmark with the prod flavor. So the variant filter looks like this

beforeVariants {
    it.enable = it.name in listOf(
        "devDebug",
        "demoDebug",
        "mockDebug",
        "prodRelease",
        "devNonMinifiedRelease", // for generating BP
        "devBenchmarkRelease", // for running benchmark
    )
}

With this the build fails during configuration:

* What went wrong:
A problem occurred configuring project ':app'.
> java.lang.IllegalStateException: The task `mergeProdBenchmarkReleaseArtProfile` doesn't exist. This may be related to a `beforeVariants` block filtering variants and disabling`prodBenchmarkRelease`. Please check your gradle configuration and make sure variants with build type `benchmarkRelease` are enabled. For more information on variant filters check out the docs at https://developer.android.com/build/build-variants#filter-variants.

It seems like the task wiring fails when a release variant (prodRelease in this case) is enabled but the corresponding benchmarkRelease variant is disabled.

Adding the prodBenchmarkRelease variant fixes it.

beforeVariants {
    it.enable = it.name in listOf(
        "devDebug",
        "demoDebug",
        "mockDebug",
        "prodRelease",
        "devNonMinifiedRelease", // for generating BP
        "devBenchmarkRelease", // for running benchmark
        "prodBenchmarkRelease", // this is never used
    )
}

But the prodBenchmarkRelease variant is useless while lot of tasks are registered for it.

I'm not sure what the right solution should be as there seems to be a chicken and egg problem when variants are being filtered out by user but also being added by the plugin during configuration.

To reproduce, please checkout this sample.

1. from app/build.gradle.kts, comment out "prodBenchmarkRelease", from line 170.
2. do a Gradle sync or run ./gradlew

---

Studio Build: Android Studio Koala 2024.1.1 Canary 3

Version of Gradle Plugin: 8.5.0-alpha03

Version of Gradle: 8.7

Version of androidx.baselineprofile: 1.3.0-alpha02

Version of Java: 21

OS: macOS