IssueTracker

it is difficult as we are talking 2 different modules. artifacts was never meant to publish things between variants and even less between modules.

what are you trying to get from such a functionality ?

If it was purely unrelated modules I would agree with you, however com.android.test is super tightly linked with the app project it instruments.

Our usecase is to build pairs of APKs needed to be sent to firebase test lab to run the tests. build.gradle links these two projects via targetProjectPath and it works from gradle, but from the onVariants API there is no way to detect this linkage.

Right now we use a really ugly workaround to make this work that i'd like to get away with.

I wonder if we should just do a punch through to give you access to the tested APK rather than the entire artifacts API ?

something like :

onVariants { variant ->
     variant.artifacts.get(SingleArtifact.TESTED_APK) // only return something if this is a test-module otherwise null.
}

wdyt ?

I only need the artifact directory and the BuiltArtifactsLoader, so if you can get those for me, that works too.

This is how we use it now for application projects https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:buildSrc/private/src/main/kotlin/androidx/build/testConfiguration/GenerateTestConfigurationTask.kt;l=122?q=artifact%20testconf%20filepath:buildSrc&ss=androidx%2Fplatform%2Fframeworks%2Fsupport

Note, to work around it we have to poke into internals of AGP APIs.

    extensions.findByType(TestAndroidComponentsExtension::class.java)?.apply {
        onVariants(selector().all()) { variant ->
            tasks.named(
                "${AndroidXImplPlugin.GENERATE_TEST_CONFIGURATION_TASK}${variant.name}",
                GenerateTestConfigurationTask::class.java
            ) { task ->
                task.appLoader.set(variant.artifacts.getBuiltArtifactsLoader())

                // The target app path is defined in the targetProjectPath field in the android
                // extension of the test module
                val targetProjectPath =
                    project.extensions.getByType(TestExtension::class.java).targetProjectPath
                        ?: throw IllegalStateException(
                            """
                        Module `$path` does not have a targetProjectPath defined.
                    """
                                .trimIndent()
                        )
                task.outputAppApk.set(outputAppApkFile(variant, targetProjectPath, path))

                task.appFileCollection.from(
                    configurations
                        .named("${variant.name}TestedApks")
                        .get()
                        .incoming
                        .artifactView {
                            it.attributes { container ->
                                container.attribute(
                                    AndroidArtifacts.ARTIFACT_TYPE,
                                    ArtifactType.APK.type
                                )
                            }
                        }
                        .files
                )
            }
        }
    }

having to use

import com.android.build.gradle.internal.attributes.VariantAttr
import com.android.build.gradle.internal.publishing.AndroidArtifacts
import com.android.build.gradle.internal.publishing.AndroidArtifacts.ArtifactType

https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:buildSrc/private/src/main/kotlin/androidx/build/testConfiguration/TestSuiteConfiguration.kt;l=178;drc=aea851191128e6cb1417dca6862f27578713bc12

Any updates here?

no news, it's on the backlog though

Probably we will need something similar for privacy sandbox artifacts as well.

Context: For macrobenchmarks of privacy sandbox projects on Jetpack CI we will need to extract not only test app APK, but also privacy sandbox dependencies (SDKs, splits, etc).

Privacy Sandbox artifacts will be exposed in b/296837048. After that can we add API to get them for target project?

Amit, looks like we need a more extensible solution than what I suggested in comment #4, I am not sure if the privacy sandbox artifacts are available to inter-project consumption but we need to devise a generic solution that works for a curated list of artifacts.

TestExtension now exposes ApkOutputProviders which can we used to fetch all apks including target project apk/s, privacy sandbox apks if the app has sdk dependency and the testing apk all matching the device spec passed as an argument. Here is the example of how to use this new API: https://cs.android.com/android-studio/platform/tools/base/+/mirror-goog-studio-main:build-system/integration-test/application/src/test/java/com/android/build/gradle/integration/privacysandbox/PrivacySandboxTestOnlyModuleApkOutputTest.kt;l=90

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
• Android Gradle Plugin 8.8.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!