A modern programming language that makes developers happier.

kotlinlang

I thought I had this Ktor networking with an MVP architecture working on iOS, but now I’m getting the following exception when trying to dispatch the result on `Dispatchers.Main`.

Anyone else running into an error like this?



you need to upgrade to  version
```1.3.9-native-mt-2```
of
```org.jetbrains.kotlinx:kotlinx-coroutines-core```


<@U013V5FK0FP> thank you so much, that got things working again!

Getting the same exception with `coroutines 1.3.9-native-mt-2` and `ktor 1.4.1`. <@U013V5FK0FP> <@UBGP9J146> any ideas? :thinking_face:

make sure you are actually using `coroutines 1.3.9-native-mt-2` and it’s not upgraded by some other dependency, you can do this (usually) by adding `!!` in the declaration

hmm, well I’m using `isForce`, since I had some issue s with `strictly` :thinking_face:

```implementation(Dependencies.Common.coroutine.Core) {
    isForce = true
}```


this exact bug (waitAll not working), was fixed in that version, so then I’d double check your dependency graph. Are you sure you have the exact same cause as the exception?  if it’s something else I’d open a new thread.

I’m not sure it’s related to `awaitAll()`.
```Fatal exception in coroutines machinery for DispatchedContinuation[MainDispatcher```
Tried using both the `Dispatchers.Main`,  and a custom one with the `dispatch_async(dispatch_get_main_queue())`   implementation :thinking_face:

if you look at the stacktrace in this thread, it’s clearly awaitAll that is the cause, which was fixed in the version I pointed out, which is why it fixed the problem. if you don’t have awaitAll in your stacktrace, you have a different problem.

You’re right, diving deeper in the stacktrace helped, looks like it’s the same as <https://youtrack.jetbrains.com/issue/KTOR-1087>