Gradle versions above 4.7 cannot resolve kotlinx-coroutines-core with GRADLE_METADATA feature enabled
See original GitHub issueWhen attempting to resolve kotlinx-coroutines-core
, Gradle versions above 4.7 show the following message:
> Could not resolve all files for configuration ':source:compileClasspath'.
> Could not resolve org.jetbrains.kotlinx:kotlinx-coroutines-core:0.26.0.
Required by:
project :source
> Could not resolve org.jetbrains.kotlinx:kotlinx-coroutines-core:0.26.0.
> Could not parse module metadata https://jcenter.bintray.com/org/jetbrains/kotlinx/kotlinx-coroutines-core/0.26.0/kotlinx-coroutines-core-0.26.0.module
> Unsupported format version '0.3' specified in module metadata. This version of Gradle supports format version 0.4 only.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:37 (9 by maintainers)
Top Results From Across the Web
Understanding Gradle Module Metadata - Gradle User Manual
Gradle Module Metadata is a unique format aimed at improving dependency resolution by making it multi-platform and variant-aware.
Read more >Error when adding buildFeatures in build.gradle file
I upgraded the Top level build.gradle file Gradle version to classpath 'com.android.tools.build:gradle:7.0.0' and distributionUrl in ...
Read more >Gradle | IntelliJ IDEA Documentation - JetBrains
Required plugins: Gradle, Gradle Extension (installed and enabled by default). The Gradle versions' support: starting with the version 3.0 ...
Read more >What's New in Gradle 6.0 - Baeldung
These features include improved dependency management, module metadata publishing, task configuration avoidance, and support for JDK 13. In this ...
Read more >Integrating Version Catalog | Medium - Umang Chamaria
Update: Version Catalog is stable in Gradle version 7.4, enabling feature is not required when using version 7.4 or above.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Are there any updates on this now that Android Studio 3.3 is in it’s release candidate stage, and is close to being released? Also, does Gradle 5.0 help this issue at all since GRADLE_METADATA is enabled by default?
It fails, but you also are enabling the features in your
settings.gradle.kts
which likely causes it: