e

    eygraber

    4 months ago
    I have an android target in my multiplatform build, and each module spams the logs with:
    The following Kotlin source sets were configured but not added to any Kotlin compilation:
     * androidAndroidTestRelease
     * androidTestFixtures
     * androidTestFixturesDebug
     * androidTestFixturesRelease
    You can add a source set to a target's compilation by connecting it with the compilation's default source set using 'dependsOn'.
    See <https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html#connecting-source-sets>
    What do I need to do to make that stop getting logged?
    Siggi Gunnarss

    Siggi Gunnarss

    4 months ago
    this is a good question. These annoyed me so much that I added something like:
    allprojects {
        afterEvaluate {   project.extensions.findByType<org.jetbrains.kotlin.gradle.dsl.KotlinMultiplatformExtension>()?.let { kmpExt ->
                kmpExt.sourceSets.removeAll { it.name == "androidAndroidTestRelease" || it.name.contains("Fixtures") }
            }
        }
    to my gradle project just to hack these source sets away. A better solution would be to figure out what fixtures is and not attach the source set to begin with, so I hope you get some more answers to your question.
    e

    eygraber

    4 months ago
    Anyone know who is attaching the android test source sets that aren't getting added to any compilation?
    joney

    joney

    4 months ago
    Hey @eygraber, thanks for sharing! Any updates on this? I have similar issues..
    e

    eygraber

    4 months ago
    No update. I've been using the snippet provided above and it's working fine for me.
    @Sebastian Sellmair [JB] is something that should be filed with AGP?