I’m having trouble using ktor http client 1.4.3 in the common layer. I can’t resolve the code in the...

# ktor

[spierce7]

I’m having trouble using ktor http client 1.4.3 in the common layer. I can’t resolve the code in the IDE. Downgrading to 1.4.2 fixes it.

[e5l]

Hey, @spierce7. It can be affected by upgrading to 1.4.20 . Could you share the project configuration and compiler version?

[spierce7]

https://youtrack.jetbrains.com/issue/KTOR-1455

[e5l]

It looks like you're still using platform dependencies. They are deprecated since 1.4.20

[e5l]

Could you specify common only dependencies in common source sets(except engines)?

[spierce7]

How would I specify the okhttp client for android?

[spierce7]

I actually didn’t even give you the build.gradle for the relevant module…

val commonMain by getting {
            dependencies {
                implementation(Deps.kotlinx.coroutines.common)
                implementation(Deps.ktor.client.common)
                implementation(Deps.kotlinx.dateTime)
                implementation(Deps.kotlinx.serialization.json)
            }
        }

val jvmMain by getting {
            dependencies {
                implementation(Deps.kotlinx.coroutines.jvm)
                implementation(Deps.ktor.client.jvm)
                implementation(Deps.okhttp)
                implementation(Deps.jsoup)
            }
        }

[spierce7]

Deps.ktor.client.common is "io.ktor:ktor-client:${Versions.ktor}"

[e5l]

Yep, I see. Could you try ktor-client-core instead?

[spierce7]

trying it now- 1.4.3 and ktor-client-core artifact in place for the common layer

[spierce7]

@e5l That appears to work. I have to sync a few times for it to take though, which is suprising

[spierce7]

@e5l Is this the solution you recommend I continue with?

[e5l]

Nope, it's a bug in kotlin-multiplatform

[e5l]

ktor-client has ktor-client-core in common dependencies

[e5l]

Nothing changes here in Ktor, but it looks like it happened with 1.4.20 kotlin update

[e5l]

Sorry for the delay

[e5l]

Can I close the issue as obsolete?

[spierce7]

So you are saying the issue should get fixed with the next bug release of Kotlin?

[e5l]

Not sure if the issue is known. Could you file the report?

[e5l]

Or we can switch subsystem of the origin issue(with fixing some details)