This message was deleted.

@allan.conda Wrap with

coroutineScope { ... }

.

I tried it, and logged the scope instance. I get StandaloneCoroutine in the calling fun and DispatchedCoroutine in that one. Ah no, I get this from withContext() I get ScopeCoroutine with your suggestion. Is this instance hanging on to the standalone one?

I don't really understand what you mean, but basically, you need this instead of what you showed:

suspend fun someBatchUpload(): List<Int> = coroutineScope {
    listOf(async { 1 }, async { 2 }).awaitAll()
}

I don’t really understand what you mean, but basically, you need this instead of what you showed:

Thanks, looks like I’m not making much sense 😄. Actually, I already came to the conclusion that I needed to use coroutineScope exactly like you wrote, because that’s the only one that didn’t throw a warning or error. But I don’t understand how it works and right now I just assume it does what I think it does; I’m not sure yet how to test scoped coroutine lifecycle so I can’t know for sure.

There's this great talk about structured concurrency: About lifecycles, it's a different thing, but Android docs should be helfup for that matter after you get stuctured concurrency

The android developers video on it is also good. I find that it’s very clear and approachable: