Are there any good use cases for launching coroutines in activities / fragments in the `lifecycleSco...

# coroutines

[Lukas Lechner]

Are there any good use cases for launching coroutines in activities / fragments in the lifecycleScope ? IMO most (all?) coroutines should be started in viewModelScope because then they continue to run on orientation changes.

[Desmond Teo]

there can be use cases for ui programming, check out https://medium.com/androiddevelopers/suspending-over-views-19de9ebd7020

[Erik]

I've seen examples of UI animations being handled in lifecycleScope

[Giorgos Neokleous]

You can expose a flow or channel (including StateFlow) from your presenter/viewmodel which then you can observe on lifecycleScope , it will act similarly to livedata. This with a combination of the launchWhenXXXX extensions

[flosch]

Or wrap a permission request in a suspendCancellableCoroutine and launch it in the lifecycleScope

suspend fun Fragment.suspendingPermissionRequest(
    permission: String
): Boolean = suspendCancellableCoroutine<Boolean> { continuation ->
    val requestPermission = registerForActivityResult(ActivityResultContracts.RequestPermission()) { result ->
        continuation.resume(result)
    }
    requestPermission.launch(permission)
    continuation.invokeOnCancellation { requestPermission.unregister() }
}

class SomeFragment : Fragment() {

    override fun onViewCreated(view: View, savedInstanceState: Bundle?) {
       super.onViewCreated(view, savedInstanceState)
        viewLifecycleOwner.lifecycleScope.launch {
            val granted = suspendingPermissionRequest(WRITE_EXTERNAL_STORAGE)
        }
    }
}

[dekans]

Most when you want to handle UI events, like clicks.
Or do actions from UI callbacks (e.g. onPrepareMenu )