Hi. Trying to set timeout on KMM, For test purposes set a pretty small value and expect to receive a...

# ktor

[Anton Afanasev]

Hi. Trying to set timeout on KMM, For test purposes set a pretty small value and expect to receive a timeout exception. On Android I am capable to receive an error, but on iOS my request execute as usual.
What am I missing?

internal fun defaultHttpClient(): HttpClient = HttpClient {
    install(HttpTimeout) {
        connectTimeoutMillis = 10
        requestTimeoutMillis = 10
    }
}

ktor 1.6.4

[Aleksei Tirman [JB]]

Seems like only the socketTimeoutMillis timeout works for the ios engine.

[Anton Afanasev]

As far as I understand there are no support for WS on ktor 1.6.4

[Aleksei Tirman [JB]]

For iOS no. Only since the 2.0.0 version.

[Anton Afanasev]

So, is socketTimeoutMillis related to the iOS REST or WS?

[Anton Afanasev]

BTW, WS was released 2 days ago, no?

[Aleksei Tirman [JB]]

So, is socketTimeoutMillis related to the iOS REST or WS?

It’s related to both.

BTW, WS was released 2 days ago, no?

The version 2.0.0 of Ktor was released a few days ago.

[Anton Afanasev]

Thanks. Now, I got it.

[Anton Afanasev]

@Aleksei Tirman [JB] Still trying to understand what would be the best approach to set timeout values that will work same way for both Android and iOS. As you mentioned before, ios engine respects only socketTimeout. Would it be correct to share this value for both platforms?
I played around with numbers and seems like Android respects the requestTimeoutMillis more than socketTimeout .
For instance setting

install(HttpTimeout) {
        socketTimeoutMillis = 10
        requestTimeoutMillis = 100
    }

will fail with:
io.ktor.client.features.HttpRequestTimeoutException: Request timeout has expired [url=http://myurl, request_timeout=100 ms]
even that socketTimeoutMillis has lower value.

Thats a little bit confusing, why...