Hey @e5l, you self assigned this issue. Is there anything I can do to help?

@e5l is this the commit? https://github.com/ktorio/ktor/commit/e6234e5b886dd1449f99414f7b769f9e204b94de

If so, is it ready to use or is it still a work in progress?

Hi @e5l, I cherry picked that commit onto the 1.2.x branch and built with mavenLocal. I made sure that this version was included in my app. I got the same crash again on Firebase, but unfortunately the stack trace does not show more information. None of the affected users (375+ users in last 7 days) so far, have reported how they got the crash. I have no idea how they get the crash. Here is the new stack trace (with coroutines debug mode enabled as well): https://gist.github.com/Thomas-Vos/75a037a2e0de62380f4b31bbf211c8d8 Is there anything I can do to help?

@e5l Does a

java.net.SocketTimeoutException

fall under a "custom state" exception?

I really need a fix for this crash as it is affecting a lot of users in my app.

I am not able to reproduce this exception myself in my app. A stack trace would really make this a lot easier. @e5l do you have any ideas?

There are some other people who responded to the GitHub issue with the same issue (https://github.com/ktorio/ktor/issues/1263)

Hello @Dominaezzz, @Santosh Astagi, @spierce7. On GitHub you responded with a similar issue. Do any of you have more details which could help solve this issue?

Here is a small example:

GlobalScope.launch {
    val deferred = async {
        val client = HttpClient(OkHttp) {
            engine {
                config {
                    // Make sure there is a timeout
                    readTimeout(1, TimeUnit.MILLISECONDS)
                }
            }
        }
        client.get<String>("<https://google.com>")
    }
    deferred.await()
}

This throws the following exception: https://gist.github.com/Thomas-Vos/adca67cc732d87691662725e56fc59b3 As you can see it does not show a stack trace referencing my code. @e5l How am I supposed to find the cause in my app? I have Kotlin debug mode enabled, but without the DebugPropes as that is not compatible with Android.

I would really like to solve it but just do not know how

One user reported that my app did not crash with WiFi off (so no timeout exception but probably an immediate socket exception). Apperantly that did not crash, but I do catch both types of exceptions so not sure why.

Did you update to 1.2.5?

check release log

Planning to use 1.2.5 and check the crash logs

Just updated to Ktor 1.2.5 and got a reported crash with a different stack trace. I think it is the same issue. Does this give someone any ideas what could be going wrong?

So, I have been digging around a bit

and I found this bug, could this be related to ktor:

kotlin native may have an issue with some segment pooling of threads. Look at the last comment @Thomas

Have you updated your app with Ktor 1.2.5? I am curios what your stack trace will be. It looks like the cause for my stack trace is happening inside an AsyncTask. I am not using them myself, The only place I can think of they are used by the system in my app are in the Android Widgets / JobIntentService. They probably use an AsyncTask in the background. But that is just a guess.

the reason I brought that up, is ktor is native, it's underlying engine may not be

We started catching SerializationExceptions, that is the only new exception, we started catching

That was a false alarm, we are seeing it again, now, but it showed up more than a week after releasing.

This has stopped happening for us now.