IssueTracker

We are currently using AGP internal task types to flag memory-intensive tasks to enforce a reduced parallelism at execution time. I've raised this separately (with a lot more detail) as a feature request (https://issuetracker.google.com/issues/224584845). However, I'm mentioning it here as our ability to implement this will be reduced or possibly eliminated by what is described int he roadmap.

Thanks #comment2 that's helpful context. I've marked that FR as blocking this and triaged it to the right component

Another use case that we have is to reactively respond to the creation of APKs and AABs. The new AGP APIs allow us to connect out tasks into the artifact pipeline via wiredWith but the best we can come up with to receive the completed artifact is to wire in toTransform. This A) does not guarantee that we will receive the final artifact as more transforms may be applied after our task is called, and B) requires us to copy the input property file/dir to our tasks output property file/dir in order to not break the build cache.

The reactive behavior of the above is the complicating factor.

A non-reactive approach could simply depend upon the task name and then look for a hardcoded path in the build directory (which is still sort of gross, since the build output paths are not documented as public API and change from time to time).

Another approach would be to wire a custom task to consume the output of the build via the built artifacts loader feeding an input property. However, this approach cannot be applied reactively. Either the custom task is included in the build and causes the creation of the binary artifact, or it is not included in the build and never gets invoked.

Re #comment4 - For artifacts exposed in the api, you should be able to just call get (example). That will always be the final artifact after all transformations

We didn't provide a task wiring helper for that case as there's only one thing to wire, but I can see how the inconsistency can be misleading

WRT #comment5, that is the scenario I was attempting to document in the last approach. The problem with that is that since the task input is set to the variant.artifacts.get(SingleArtifact.APK)), if the task is included in the build it will cause the creation of the artifact. Our build is currently defined to reactively perform some actions (predominantly some fancy reporting) only if work is actually performed.

We had previously been pushing our build to wire in to task outputs by locating tasks by type and referencing output properties as inputs to tasks registered via task finalizes or dependsOn relationships. This started getting more and more fragile as the AGP APIs migration proceeded/matured. I'm to the point now where I think the notion of reactive execution is hostile to the direction/expectations of both Gradle and AGP and want to start moving away from it, yet our build as it currently stands does rely on this behavior.

I bring up this up as a gap only because I don't know if I'll be able to completely refactor our CI pipeline's expectations in time for Gradle 8+.

I think that's a fair request. Being able to have a task that consumes an artifact but finalize the final task that touches that artifact makes sense. We can look into this.

Note that we have changed our timeline. The old API will only be removed in 9.0. see our updated roadmap for more details.

Another minor functionality gap: We have a build that has test coverage enabled during test execution but then we manually disable the coverage report generation for all project modules as we have a custom coverage report task that creates an aggregate test coverage report for the entire project. This saves us the execution time, I/O, and protects us from Jacoco implementation instabilities.

We're currently using the following to accomplish this:

            project.tasks.withType(JacocoReportTask::class.java) {
                enabled = false
            }

Another gap, though my perhaps there's a better way to express this? Some of our builds leverage Flank to run instrumentation tests on Firebase Test Lab. These builds run as a single CI stage so as to afford Gradle the best opportunity to parallelize work. In this context, we have found that prioritizing instrumentation test assembly work early in the build allows the tests to dispatch to FTL earlier, minimizing overall build times. To implement this, we have chosen to be explicit on the inverse side by pushing lint and local unit test execution to be shouldRunAfter the flank tasks which in turn depend on the instrumentation test assembly, etc.

Specifically:

    private fun bumpFlankTask(project: Project, flankTasks: TaskCollection<FlankExecutionTask>) {
        listOf(AndroidLintTask::class.java, AndroidLintAnalysisTask::class.java, AndroidUnitTest::class.java)
            .forEach {
                project.tasks.withType(it).configureEach {
                    shouldRunAfter(flankTasks)
                }
            }
    }

This seems fairly specific to our project's desires and not necessarily transferable to other projects. I think our best option for the future Gradle 9+ might be to fallback to leveraging task names rather than leveraging task types in a generic fashion. Mentioning it here in case there is a better approach/option once the types are no longer available.

Another gap we've found but no longer directly depend upon: when invoking BundleToStandaloneApkTask the resulting universal APK does not appear to be accessible via the Artifacts API / ArtifactType.APK - at least as of AGP 7.0.

We are able to no longer directly depend upon it because we are using the task name and a hardcoded build output directory path to locate the APK if/when it gets built. This is another symptom of our reactively defined build implementation. However, if we were to relay on #comment8 coming to fruition then we'd likely be able to leverage that instead of the hardcoded path approach.

(phew! I think that's it for now? sorry for the dump, we're just starting to get caught up!)

That last one (Comment #11) seems like a bug. Jerome?

Ran into another use case that the API does not yet seem to support: AndroidUnitTest configuration for offline Jacoco instrumentation. Given that we've had to tweak task outputs to get this to work reliably with the build cache it is probably best corrected on the AGP side. Probably easiest just to paste the relevant code here:

        /*
         * -Djacoco-agent.destfile arg is used to configure the offline mode behavior of jacoco.  The offline
         * behavior is what is used when dependency module code is executed as it has already been
         * instrumented by the jacoco-agent in previous executions.  We redirect this to record the offline
         * results under the build directory and give it a more explicit/identifiable name (it defaults
         * to the project dir as jacoco.exec).
         *
         * NOTE: Attempts at using JacocoTaskExtension.setDestinationFile were unsuccessful in capturing coverage
         */
        project.tasks.withType(AndroidUnitTest::class.java).configureEach {
            val execFile = project.layout.buildDirectory.file("jacoco/offlineDependencies.exec").get()
            jvmArgs("-Dfile.encoding=UTF-8", "-Djacoco-agent.destfile=${execFile}")

            // Register our file as a task output to ensure it is restored via the build cache when execution is avoided
            outputs.file(execFile)

            doFirst {
                // Make sure the coverage file is removed if it exists from a previous run
                execFile.asFile.deleteRecursively()
            }
        }

And one question:

We have some convention plugin code which is applied to many project module. It uses the components extension's onVariants callback to reactively trigger some data capture but needs to know whether or not minification has been enabled for the build type, configured by a separate convention plugin. We have code similar to the following:

        project.plugins.withId("com.android.application") { plugin ->
            val extension = project.extensions.getByType(ApplicationAndroidComponentsExtension::class.java)
            val android = project.extensions.getByType(ApplicationExtension::class.java)
            extension.onVariants { variant ->
                ...
                if (android.buildTypes.getByName(variant.buildType!!).isMinifyEnabled) {
                    ...
                }

ApplicationExtension feels like more of an input API for AGP and not something we should be programmatically querying within the onVariants callback. Given the exposure of other configuration values (e.g. variant.pseudoLocalesEnabled as Property<Boolean>), should isMinifyEnabled also be exposed?

Alex, can you look at #11 first, then at #13.

#14, yes, it should probably be offered in ApplicationVariantBuilder.

Alex and I looked a bit more carefully and we cannot make APK the result of the bundleToAPK task. The reason is that only one task can produce an artifact type at a time.

You cannot have an artifact type being produced by either the normal APK packaging task or the APKFromBundle task depending on what the user requested. In particular, if any script/plugin request the public APK artifact type, which task is supposed to run ?

The only way we can somehow satisfy #11 would be to have another public artifact type called APK_FROM_BUNDLE which would ensure that the bundle is created first, then the APK from the bundle. would that work ?

We should really file separate bugs for all these comments. We can't just use a single bug for all of this.

I filed the following specific bugs:

• comment #4 -> Issue 232323922
• comment #9 -> Issue 232324065
• comment #11 -> Issue 232325458
• comment #14 -> Issue 232325329

I have not yet filed anything related to Jacoco, as we probably need to discuss things a bit internally first.

We develop a convention plugin which adds some code quality tasks(detekt, checklist, lint) to the build, whenever assemble task is invoked. We achieved this on the old api by obtaining the assemble task provider with BaseVariant.getAssembleProvider() method then adding our tasks as a dependency to it. However, I couldn't find any equivalent method in the new Variant API. I thought of registering a custom Default task, which depends on SingleArtifact.APK and all of our other custom tasks, then host apps could use this new task on their local and CI machines to create apk. However, this method is not optimal since some developers still can run the assemble task directly and bypass our code quality tasks and also, this new task will not be executed when developers run their project on the Android Studio by default. So I would like a way to include some tasks to the artifact creation even if they do not produce or use this artifact. What I can suggest is a way to make artifacts depend on tasks similar to how tasks can depend on artifacts. For instance, something similar to the following would solve our use case:

variant.artifacts.get(SingleArtifact.APK).getTaskProvider().configure {
    it.dependsOn("detekt${variant.name.capitalize()}")
}

Currently, what we are doing to solve this problem is the following:

project.extensions.getByType(AndroidComponentsExtension::class.java).onVariants { variant ->
    project.afterEvaluate {
        project.tasks.named("assemble${variant.name.capitalize()}").configure {
            it.dependsOn("detekt${variant.name.capitalize()}")
        }
    }
}

which I know is not recommended. Therefore, could you consider adding a new api for this case?

Another thing is I couldn't find a way to obtain "lint" task for the current variant without tasks.named("lint${variant.name.capitalize()}"). Could you also create a method to obtain lint task for the current variant, add dependency tasks for it. Adding dependency for lint is important for us since we download our lint configuration with a custom task and we want this configuration to be ready when "lint" needs it. (This case could also be solved by using Provider API in the lint block of the finalizeDsl, however currently the "lintConfig" property is declared as File in this block)

And lastly, it would be nice if InternalArtifactType.JAVA_DOC_DIR was a public artifact. If our convention is applied to a library project, whenever we publish the aar, we also publish its javadoc(and kdoc) to a remote server. For this we need to add custom Javadoc task and configure it properly for the variant. However, I think, this process is a bit complex. I could not properly configure the custom Javadoc task using the new variant api. With the old API I was using the following configuration:

source = variant.getJavaCompileProvider().get().source
classpath += project.files(project.provider { androidExtension.bootClasspath })
classpath += project.files(variant.getJavaCompileProvider().map { it.classpath })

Therefore, making InternalArtifactType.JAVA_DOC_DIR public would greatly simplify our implementation and solve our problems. Currently, only solution I found was to add dependency to "javaDoc${variant.name.capitalize()}Generation" task and hardcode its output path as "intermediates${File.separator}java_doc_dir${File.separator}$componentName". But I know this is really fragile and would love to see an easier and more conventional way to accomplish this.

I'm developing a plugin for external sources compilation into *.so files.

How can I inject final *.so files into the final APK/AAR? I saw that AGP has AndroidArtifacts.ArtifactType.JNI{_SHARED} But I have no idea how to use it and can't find any samples. I also can't put SingleArtifact.APK because it is transformable but not appendable.

variant.artifacts.use(task)
    .wiredWith { it.outputSoFolder }
    .toAppendTo(...) // <-- what to put here?

EXTRA: how to add their debug symbols to LLDB during debugging from the plugin (same as Makefiles/CMake does).

AndroidArtifacts.ArtifactType is internal and not meant to be used by our API. The thing to pass to toAppendTo would have to be a MultipleArtifact but we don't expose many of them yet, and none that are useful for your use case.

At some point we may expose the intermediate artifact that is the final folder of all the .so files, but that may not be what you want either. If it's the final folder, then it's a single folder, so you cannot append to it, and you can only transform it (which means taking the content, processing it, and writing the output in a different folder). This is not efficient when you want to add new files to it.

So, your use case actually is better positioned to use sourcesets rather than inject in an intermediate. We recently introduced Component.sources which gives access to the different sources for a variant, and allows adding build-generated ones. This is the entry point you need.