About Fragment implements CoroutineScope example, ...

# android

[itnoles]

About Fragment implements CoroutineScope example, does cancel method needs on onDestroy()?

[gildor]

sure

[gildor]

But I would recommend to always use LifecycleOwner.lifecycleScope and do not implement own scope for Fragments and Activities

[itnoles]

https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/-coroutine-scope/ hmm

[gildor]

One more problem with Fragment and CoroutineScope, that if you have any coroutine that bound to View lifecycle rather than to Fragment lifecycle it’s too easy accidentally to use launch of Fragment scope

[gildor]

Probably make sense to remove this example, because it confuses Android users and encurage to implement own scopes

[gildor]

again, Fragment is not different from Activity in general, you have to cancel scope onDestroy

[itnoles]

Do you have examples somewhere?

[gildor]

of what?

[itnoles]

Lifecycle and implementing own scope

[gildor]

Implementing own scope is just like in doc which you shared above

[gildor]

For lifecycleScope see Android libs documentation
https://developer.android.com/topic/libraries/architecture/coroutines

[gildor]

But I recommend to use lifecycleScope, it’s safer (no chance that you forgot to cancel scope, explicit separation of Fragment and View lifecycles), less code, more flexible for fragments (no need to create and manage view scope)