Is it possible that the scope will be canceled before the `DisposableEffect`'s onDispose is called? ...

# compose

[Nick]

Is it possible that the scope will be canceled before the `DisposableEffect`'s onDispose is called?

val scope = rememberCoroutineScope()
DisposableEffect(Unit) {
    onDispose {
        // do some stuff
        scope.launch { < -- could this be canceled when the call leaves the composition?
            // tear down
        }
    }
}

[Loney Chou]

Hmm, why do you need to manually cancel that

[Zach Klippenstein (he/him) [MOD]]

@Adam Powell Do we make any guarantees about ordering here?

[Adam Powell]

so long as the apply dispatcher for the composition is serialized, that scope.launch 's suspend function won't have an opportunity to run before scope is cancelled, but `onDispose {}`'s block does indeed run before that cancellation occurs

[Nick]

So I think if I understand what you said correctly, it's best if we do not use the scope from rememberCoroutineScope, rather we should use some other scope that has a longer lifecycle.

DisposableEffect(Unit) {
    onDispose {
        someLongerScope.launch {
            cameraProvider?.unbindAll()
        }
    }
}

[Zach Klippenstein (he/him) [MOD]]

If you’re just doing non-suspending cleanup operations that need to run after the frame completes you can pass NonCancellable as the context to launch. But that’s dangerous if anything could suspend, since it could leak.

[Adam Powell]

If you're just unbinding camerax stuff iirc that doesn't suspend; do it directly in the onDispose block and skip the launch entirely