I posted this over in ktor but in case people here...

# kotlin-native

[HankG]

I posted this over in ktor but in case people here may have an answer. I think I have a library version clash going on. I'm using coroutines 1.3.9-native-mt, serialization 1.0.0, and ktor version 1.4.0 or 1.4.1 running the SpaceXAPI code snippet but I get Uncaught Kotlin exception: kotlin.IllegalStateException: Cannot execute task because event loop was shut down with the CIO client explicitly selected when creating the HttpClient. It's code that works under the JVM though.

[John O'Reilly]

not a direct answer to your issue but I am using similar combinations of versions in https://github.com/joreilly/PeopleInSpace and https://github.com/joreilly/BikeShare if you want to compare. These are multiplatform projects but do include KN targets.

[John O'Reilly]

I did btw run in to following issue when using Ktor 1.4.1 - https://youtrack.jetbrains.com/issue/KTOR-1087

[HankG]

Thanks!

[HankG]

Yeah trying a combination of versions.

[HankG]

Drop into one of the RC's of serialization and the Json initialization stuff seemed to get wonky

[John O'Reilly]

there's certainly some constraints around how those versions can be combined

[HankG]

I know ktor has some single vs. multithreaded coroutine sensitivities but I thought this was the right combo for that

[John O'Reilly]

in PeopleInSpace for example I'm using

const val kotlin = "1.4.10"
    const val kotlinCoroutines = "1.3.9-native-mt"
    const val ktor = "1.4.0"
    const val kotlinxSerialization = "1.0.0-RC"

[John O'Reilly]

btw note the isForce use in https://github.com/joreilly/PeopleInSpace/blob/master/common/build.gradle.kts ...not having this might be causing you issue

[HankG]

Yeah I tried that with

implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:$coroutinesVersion") {
                    version {
                        strictly(coroutinesVersion)
                    }
                }

[HankG]

I'll try your way see if that fixes it

[John O'Reilly]

yeah, strictly is I think the more recommended approach and meant to change to use that....don't think it should behave differently to isForce

[HankG]

yeah same effect

[HankG]

Further progress but hit wall, I think with ktor native. needed to do runBlocking(newSingleThreadContext) (default and unconstrained didn't work) but now CIO says TLS sessions aren't supported on native...well darn...

[HankG]

...Curl client works and doesn't have the coroutine event loop error problem...I'm wondering if that was a false trail...going to post final working code example once clean it up and blog about it.