Ok this one is really killing me now: `Could not resolve io.ktor:ktor-client-js:1.6.0` error every t...

# ktor

[darkmoon_uk]

Ok this one is really killing me now:
Could not resolve io.ktor:ktor-client-js:1.6.0
error every time at Gradle sync. But...
• The project does build and run ✅
• The artifact name is correct
• I've added <https://repo1.maven.org/maven2/> repo directly to the using project
• The artifact is there
• All other Ktor artifacts are resolving just fine.
• I've cleared build and ~/.gradle folders
I am using js(IR){...} target, in case this has to do with resolving IR variant(?)
...nearly at a loss.

Is anyone else seeing weird stuck artifact mis-resolution around Ktor?

[darkmoon_uk]

I'm using Android Studio, but got the same result from IntelliJ after I stripped out the Android stuff.

[darkmoon_uk]

So far looks like a bug in:
org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.10

[Dominaezzz]

Which version of gradle are you using?

[darkmoon_uk]

https://drive.google.com/file/d/16l1_GerT547BhtcZiIySKROi9oWiAEiX/view?usp=sharing

[darkmoon_uk]

@Dominaezzz 7.0.2

[darkmoon_uk]

I just trimmed down to this reproduction project ☝️

[darkmoon_uk]

Might be able to trim further but this seemed like a reasonable place to stop.

[Dominaezzz]

Ah, I reckon that version might be too high. This might be a #multiplatform issue.

[darkmoon_uk]

I am prepared to raise a YouTrack, but if anyone cares to try and Gradle sync this project in IDE and just confirm the error, I'd have added confidence that I'm not wasting JB's time.

[darkmoon_uk]

My result is that ./gradlew assemble succeeds but Gradle Sync in IDE does not.

[darkmoon_uk]

@Dominaezzz Thanks I'll try that variable...

[darkmoon_uk]

Noted current KMP samples are using Gradle 6.5

[darkmoon_uk]

Same error w/ Gradle 6.5 🙅

[darkmoon_uk]

Raised: https://youtrack.jetbrains.com/issue/KTIJ-15989

[e5l]

@dsavvinov @h0tk3y

[dsavvinov]

Thanks for the minifying and reporting the issue! We’ve taken a look at it, and apparently when we were adding Gradle attributes for IR/Legacy JS targets, we’ve missed a few configurations. They are used exclusively by IDE Sync, that’s why the build finishes successfully, but sync fails. The fix should arrive in 1.5.30 (maaaaaaybe in 1.5.20, but that’s highly unlikely)