hi guys, given ```viewModelScope.launch(<http://Dispatchers.IO|Dispatchers.IO>) { block() fo...

# coroutines

[Joseph D]

hi guys, given

viewModelScope.launch(<http://Dispatchers.IO|Dispatchers.IO>) {
    block()
    foo1()
}

If block’s body contains

viewModelScope.launch(Dispatchers.Main) {
            foo2()
        }

foo1() is never executed. can somebody explain me why?

[zak.taccardi]

is your block() suspending?

[octylFractal]

is that the entirety of block()?

[fatih]

Are you cancelling the scope somewhere?

[Joseph D]

is your block() suspending?

yes sir (hi, i know from twitter, what’s up)

is that the entirety of block()?

no, that code is executed during flow.collect{} method

Are you cancelling the scope somewhere?

no i am not

[octylFractal]

hmm, I think i'd have to see more code -- flow.collect {} sounds like it might be the issue, but if it only happens when you add that launch, I can't make sense of it

[Joseph D]

thanks for the private help, @octylFractal. problem was block() throwing

kotlinx.coroutines.JobCancellationException: Job was cancelled; job=SupervisorJobImpl{Cancelling}@e1ab056

I will investigate why

[Daniel]

why not use withContext()

[octylFractal]

it has different semantics to launch?

[Joseph D]

I understood the issue: block() shows a new fragment -> Viewmodel#onCleared is called -> viewModelScope’s job is canceled. when foo1() is called, the job was canceled.

[Joseph D]

any elegant solution to this? 🙂

[octylFractal]

assuming you just need to cleanup resources, finally is probably a good option here