I’m trying to run some tests on JVM/iOS/JS targets with `MockEngine` and it works on the JVM and JS ...

# ktor

[KamilH]

I’m trying to run some tests on JVM/iOS/JS targets with MockEngine and it works on the JVM and JS targets, but fails on iOS with following message:

kotlin.Error: Ktor native HttpClient requires kotlinx.coroutines version with `native-mt` suffix (like `1.3.9-native-mt`). Consider checking the dependencies.

Where should I add those dependencies? I though I should add it in iosTest like that:

sourceSets {
        val iosTest by getting {
            dependencies {
                implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.9-native-mt")
            }
        }
}

but it doesn’t help. Adding to iosMain also doesn’t change anything

[KamilH]

Here is a test code:

class HttpClientTest {

    private val httpClient: HttpClient = HttpClient(MockEngine) {
        engine {
            addHandler {
                respondOk()
            }
        }
    }

    @Test
    @JsName("testResponse")
    fun `test response`() = runTest {

        val response = httpClient.get<HttpResponse>("<http://www.google.com|www.google.com>")

        assertEquals(response.status, HttpStatusCode.OK)
    }
}

[e5l]

Hey, @KamilH, could you file an issue with reproducer? I will take a look

[KamilH]

Sure, on YouTrack?

[e5l]

Yep

[Tijl]

don’t add it to iosMain, add it to commonMain. and use !! to enforce the version: implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.9-native-mt!!")

[Tijl]

note there is a 1.3.9-native-mt-2 by now as well

[e5l]

Yep, we also allow native-mt-2 and any compatible with native version. There is runtime check for that

[KamilH]

@Tijl Thank you it’s working now
@e5l Would you still like me to file the issue?

[e5l]

Yep, in Kotlin. It's tooling problem

[Nikolay Kasyanov]

hey folks, do I get it right that the workaround is to put the coroutines dependency into commonMain?

[Tijl]

I mean, it’s not really a workaround, it’s the normal way of doing things.

[Nikolay Kasyanov]

I agree, although then I’m confused what bug the OP was asked to file

[KamilH]

At the and of the day I didn’t file a bug, because I didn’t know what to file 😅

[Nikolay Kasyanov]

I see, thanks 🙂

[Anvith]

@Tijl This enforcement (!!)causes Intellij to break and all syntax highlighting to disappear since it cannot resolve the artifact, strangely though commandline works and generates stuff.
I ended using 1.3.9-native-mt-2 along side the gradle force flag for it to work perfectly with both

implementation(CommonDeps.coroutinesCore){
           isForce =true
    //newer gradle directive  of 'strictly' doesn't work for some reason either
  }

[KamilH]

@Anvith thanks for sharing this info. Just yesterday I was testing my library that is using 1.3.9-native-mt!! and it was working properly when integrated into Android app, but suddenly it stopped working. I spent some time investigating and I’ve found nothing about that. Changing to 1.3.9-native-mt-2 in Kotlin Multiplatform library solved an issue. So strange

[Tijl]

I guess it’s an intellij regression then? I’m using Android Studio, which usually uses a lower IJ version as it’s base, seems fine here. I think (not sure) !! is a shortcut for strictly.