mega Finally we have the last release candidate `1 3 0 rc2`

Question

mega Finally we have the last release candidate `1 3 0 rc2` It s time to test and migrate the final release is coming after New Year Holidays See the migration page <https ktor io quickstart migration 1 3 0 html> christmas tree Please note that we have long New Year Holidays here so no worries if we don t respond quickly

Aleksey Chugaev · Answer

Does this release work with background threads on native targets iOS

cy · Answer

I hope so it should

napperley · Answer

Does this release include support for the Linux targets with Ktor Server

Dmitri Sh · Answer

< cy> any chance you guys could take a look at this web sockets problem I have had for a while unknown protocol ws ```try method = HttpMethod Get host = hostn port = portn path = ws send Frame Text Android client connecting ``` I originally experienced this with an android phone client and then it just went away on its ownAdded a wearos project same problem they are both using the same shared common lib but here it s just not going away

Dmitri Sh · Answer

by went away on its own I mean I didn t do anything had this error continuously for a number of builds and then suddenly it worked I don t know how to explain it Unfortunately no such mysterious luck with the wearos counterpart

cy · Answer

< napperley> No it is planned to 1 4 0

cy · Answer

< Dmitri Sh> it looks like you are trying to use Android Client engine with websockets that is not supported and will never be supported due to the underlying implementation Use OkHttp or other engines for websocket support

Dmitri Sh · Answer

< cy> well it does work with Android phone client And I use cio engine here is my two source sets for common and android ```sourceSets commonMain dependencies implementation org jetbrains kotlin kotlin stdlib common implementation org jetbrains kotlinx kotlinx coroutines core common 1 3 3 Serialize implementation org jetbrains kotlinx kotlinx serialization runtime common 0 14 0 implementation io ktor ktor client core $ktorversion implementation io ktor ktor client json $ktorversion implementation io ktor ktor client logging $ktorversion implementation io ktor ktor client serialization $ktorversion implementation io ktor ktor client websockets $ktorversion implementation io ktor ktor client cio $ktorversion sourceSets androidMain dependencies implementation org jetbrains kotlin kotlin stdlib implementation org jetbrains kotlinx kotlinx coroutines android 1 3 3 implementation io ktor ktor client android $ktorversion implementation io ktor ktor client core jvm $ktorversion implementation io ktor ktor client json jvm $ktorversion implementation io ktor ktor client logging jvm $ktorversion implementation io ktor ktor client serialization jvm $ktorversion implementation io ktor ktor client websockets jvm $ktorversion implementation org jetbrains kotlinx kotlinx coroutines core 1 3 0 ```

cy · Answer

So you include both

cy · Answer

You need to include only one to be sure

cy · Answer

Or specify it when creating a client

Dmitri Sh · Answer

ok thanks will try later today is there any ref documentation on how to specify the engine when creating a client

Dmitri Sh · Answer

< cy> so I commented out android client and left just cio now it works on both phone and wear os many thanks I am still puzzled though both phone and wearos are really the same thing using the same source set and android client did work with web sockets for the phone but not wear os Strange If you have a chance is there anything else that is off in my sets

cy · Answer

See <https ktor io clients http client engines html> about client engines

Dmitri Sh · Answer

thanks checking it out

Aleksey Chugaev · Answer

I have submitted an issue for background threads on native targets iOS <https github com ktorio ktor issues 1538>