do you know if

SharedFlow

is available from

org.jetbrains.kotlinx:kotlinx-coroutines-core:1.4.1

? if not, which dependency shall I add for the

commonMain

sourceset?

The scope you want to run your coroutine in

as far as I know the only available scope from iOS is provided by

runBlocking

but that doesn’t work. I’ve tried a custom implementation that doesn’t work either:

internal actual fun CustomMainScope(): CoroutineScope = CustomMainScopeImpl()
internal class CustomMainScopeImpl : CoroutineScope {
    private val dispatcher = MainDispatcher()
    private val job = Job()
    private val exceptionHandler = CoroutineExceptionHandler { _, throwable ->
        println("${throwable.message}: ${throwable.cause}")
    }
    override val coroutineContext: CoroutineContext
        get() = dispatcher + job + exceptionHandler
}
private class MainDispatcher : CoroutineDispatcher() {
    @Suppress("TooGenericExceptionCaught")
    override fun dispatch(context: CoroutineContext, block: Runnable) {
        dispatch_async(dispatch_get_main_queue()) {
            try {
                block.run()
            } catch (err: Throwable) {
                throw err
            }
        }
    }
}

Maybe I’m missing something very obvious here :S

Uh no you have all the usual scope. You can try

MainScope()

to run it on the UI thread

I’m not sure how a hot stream through a StateFlow can work on the main thread without blocking the entire application though :S

You can make a scope from a new thread with something like

CoroutineScope(newSingleThreadContext("Test"))

yup but

newSingleThreadContext

is not part of coroutines 1.4.1, is part of the

-native-mt

and as far as I know the mt branch version does not support StateFlow yet

Oh, yeah. You can’t do multithreaded coroutines outside the native-mt branch obviously, you just have the main thread

ok so on 1.4.x state flow is broken from iOS because it will completely block the main thread, is that correct?

I would not recommend frankensteining a dispatcher for outside the main thread yourself

he yup, oki

I can’t wait for stateflow either 🙂

@Ferran If you need to use coroutines only on the main thread, you can use that dispatcher until Kotlin/Native gets a new memory model and

Dispatchers.Main

gets working on iOS (or there's a newer

native-mt

version, in the meantine): https://github.com/Kotlin/kotlinx.coroutines/issues/470#issuecomment-440080970

I’ll give it a go, thanks @louiscad!