android-coroutines

To safely collect Kotlin flows during the Android lifecycle, use repeatOnLifecycle within lifecycleScope to ensure collection only occurs when the lifecycle is active, preventing crashes and resource waste.

To achieve main-safe suspend functions, use dependency injection to pass dispatchers via constructors. This allows easy context switching for background work and facilitates reliable testing using TestDispatcher.

To test Kotlin coroutines in Android using runTest, replace real dispatchers with a StandardTestDispatcher. This eliminates flakiness by controlling virtual time and ensuring structured concurrency in ViewModel and repository tests.

Use SupervisorJob and CoroutineExceptionHandler when you need to prevent a child coroutine failure from cancelling siblings and to centrally manage uncaught exceptions. This maintains structured concurrency without prematurely terminating the scope.

To convert callbacks to Kotlin flows using callbackFlow, bridge existing callback-based APIs into reactive streams. This suspends execution and manages resource cleanup automatically upon cancellation, integrating legacy code with structured concurrency.

Your Android ViewModel coroutine leaks memory across configuration changes if it is not launched within viewModelScope. Using viewModelScope ensures structured concurrency and automatic cancellation when the ViewModel is cleared.