IssueTracker

Thanks for reporting this. We will investigate this and get back to you once we have an update.

The issue has been fixed and merged to Android Open Source Project. The fix should be available in the next tv-compose release (Version: 1.0.0-alpha04).

Closing this ticket. Feel free to re-open in case of any issues.

Thanks 😀

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.tv:tv-material:1.0.0-alpha04

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.

So far we have found that from alpha12 (good version) to alpha13 (bad version) of androidx.sqlite, one change that affected the metadata was the upgrade from Gradle 8.11.1 to 8.12, this is a diff of the metadata: https://diff.googleplex.com/#key=2ZkNTETNoG0R.

Notice the removal of the org.gradle.libraryelements attribute. The attribute is also missing with Gradle 8.13-rc1

Update on libraryelements attribute missing in jvm target publications with Gradle 8.12 - Jetbrain are saying it will be fixed after https://youtrack.jetbrains.com/issue/KT-36004/Update-org.gradle.usage-attribute-rules-to-support-the-JAVAAPI-and-JAVARUNTIME-value which is targeting KGP 2.1.21. Temporary fix could be for androidX to explicitly set libraryelements attribute to "jar" for the jvm api/runtime elements publications.

By the way I have noticed a weird behaviour - if you do ./gradlew publish in your project libraryelements is not there for jvm publications but if you do ./gradlew publishJvmPublicationToMavenRepository it's there

Daniel, Owen, let me know if this is enough info to proceed further with a fix.

For the issue of the android publications where "org.gradle.libraryelements" = "jar" instead of "aar" - that was fixed in AGP 8.10 canary 7. Please feel free to try it out and report back. Thank you

FYI danysantiago@ we have upgraded to 8.10.0-alpha07 in androidx.