IssueTracker

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

Thanks for reporting this issue.

COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.

Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.

This will be fixed in AGP 8.5.0-alpha04 and also will be backported to 8.4.0 RC2 and stable

It breaks on the consumer side, not the publishing side.

That is correct. Older AGP versions with Kotlin Gradle Plugin applied did not set enough attributes when resolving the dependencies resulting in the wrong platform being picked up.

The only way for this to work again would be for compose to stop publishing -desktop platform of compose and we don't think we are willing to do that.

How much control do you have over your consumers? You could potentially create a Gradle plugin that tweaks AGP configurations in older versions.

Yes KGP should just work.

Indeed, 8.3 is the latest stable version at this point. 8.4 (and the corresponding IDE Jellyfish) is still in beta stage as you mentioned. The fix in AGP will go out in 8.4 RC2 (it missed the boat for RC1) and subsequently stable.

As comment #3 mentioned, you should be able to manually force the variant by explicitly applying the variant selection attribute:

KotlinPlatformType.setupAttributesMatchingStrategy(project.dependencies.attributesSchema)
androidComponents.onVariants { variant ->
    variant.components
        .flatMap { listOfNotNull(it.runtimeConfiguration, it.compileConfiguration) }
        .forEach { configuration ->
            configuration.attributes.apply {
                attribute(KotlinPlatformType.attribute, KotlinPlatformType.androidJvm)
            }
        }
}

Gradle's variant resolution is unfortunately very difficult to understand, but essentially this tells gradle to prefer the android artifacts whenever they're available.

As AGP we can't do much about this fact that people can't upgrade to the latest version. Essentially the issue stems from a discrepancy in the way KGP publishes multiplatform libraries and the way AGP consumes them. This problem is now fixed and in AGP 8.4 RC2 (and 8.5 canary 4). From KGP side the problem is also fixed - please refer to https://youtrack.jetbrains.com/issue/KT-49919/Introduce-the-org.gradle.jvm.environment-attribute-on-JVM-and-Android-published-variants-both-for-MPP-and-non-MPP-libraries for more context.

Additionally, if you are a library developer and want to target android only you could consider not depending on androidx.compose.runtime:runtime (which exposes -android and -desktop variants) but directly depend on the androidx.compose.runtime:runtime-android (https://maven.google.com/web/index.html?#androidx.compose.runtime:runtime-android) artifact - I think this is should work - feel free to correct me if not.

Additionally, if you are a library developer and want to target android only you could consider not depending on androidx.compose.runtime:runtime (which exposes -android and -desktop variants) but directly depend on the androidx.compose.runtime:runtime-android (https://maven.google.com/web/index.html?#androidx.compose.runtime:runtime-android) artifact - I think this is should work - feel free to correct me if not.

it does not really work that way as each -android variant will pull in root non-android ones.

A postmortem task was automatically filed as a child item to this bug.

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 Jellyfish | 2023.3.1
• Android Gradle Plugin 8.4.0

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!

Help

Help