IssueTracker

Is this not a bug in AGP? It doesnt feel like an androidx issue.

Probably yes, feel free to reroute or CC the right people. I was not 100% sure since the project uses the androidXMultiplatform DSL, but looking at the DSL it simply forwards things to AGP.

Do you have an example of what a broken consuming project looks like? which plugins are they applying?

I've uploaded a sample project, to repro run: ./gradlew test

It is a simple Kotlin JVM project, it only uses plugins { kotlin("jvm") version "2.1.10" }

I was also able confirm that without AGP KMP (aosp/3493350) the project works as expected.

Looking at the Gradle metadata diff (https://diff.googleplex.com/#key=EY2FqaJWQbUQ), maybe the issue is the addition of "org.gradle.libraryelements": "jar" ? Should that be an aar instead? ` https://screenshot.googleplex.com/hjNF5GgDDC5CYEt

yes, androidApiElements/runtimeElements variant publications should have aar value on the libraryelements attribute. What version of Gradle, AGP, KGP are you using in your library?

What's bizarre is that the compileClasspath is using the jvm vairant (in the test project you shared), it's only at runtime that it resolves the -android artifact of your library...

It's very confusing, though why the android variant is chosen.

./gradlew dependencyInsight --configuration runtimeClasspath --dependency  androidx.sqlite:sqlite:2.5.0-beta01

> Task :dependencyInsight
androidx.sqlite:sqlite:2.5.0-beta01
  Variant androidRuntimeElements-published:
    | Attribute Name                     | Provided     | Requested    |
    |------------------------------------|--------------|--------------|
    | org.gradle.status                  | release      |              |
    | org.gradle.category                | library      | library      |
    | org.gradle.jvm.environment         | android      | standard-jvm |
    | org.gradle.libraryelements         | jar          | jar          |
    | org.gradle.usage                   | java-runtime | java-runtime |
    | org.jetbrains.kotlin.platform.type | jvm          | jvm          |
    | org.gradle.dependency.bundling     |              | external     |
    | org.gradle.jvm.version             |              | 21           |

org.gradle.jvm.environment=standard-jvm is obviously requested and it doesn't match with the provided value for android. Looking at the jvmRuntimeElements from the diff you supplied of the gradle meta file, we see

    {
      "name": "jvmRuntimeElements-published",
      "attributes": {
        "org.gradle.category": "library",
        "org.gradle.jvm.environment": "standard-jvm",
        "org.gradle.usage": "java-runtime",
        "org.jetbrains.kotlin.platform.type": "jvm"
      },
      "available-at": {
        "url": "../../sqlite-jvm/2.5.0-beta01/sqlite-jvm-2.5.0-beta01.module",
        "group": "androidx.sqlite",
        "module": "sqlite-jvm",
        "version": "2.5.0-beta01"
      }
    }

So every attribute in the jvmRuntimeElements matches the requested ones.

Oh,i missed the libraryelements one from the list. Looks like jvmRuntimeElements does not publish that attribute and the android one does (and it's a wrong one as mentioned before). So it looks like that could the reason for the wrong variant resolution.

The library is from androidx, we are using 8.9.0-beta01

I did also notice the compile classpath is fine, after all it compiles correctly and the APIs do resolve in the IDE, but at runtime it fails.