android-coroutines

To prevent lifecycle leaks when collecting Kotlin Coroutines Flow, use repeatOnLifecycle with lifecycleScope to ensure collection only occurs during active lifecycle states, automatically canceling jobs when the UI is destroyed.

Structured concurrency in Android Kotlin Coroutines enforces parent-child job hierarchies across ViewModel and Repository boundaries, ensuring child coroutines are automatically canceled when their parent scope is cleared, preventing memory leaks.

Maintain main-safety by injecting CoroutineDispatcher instances into ViewModels and Repositories rather than hard-coding Dispatchers, ensuring blocking operations run on background threads and UI updates resume on the main dispatcher.

Test Kotlin Coroutines in Android by using runTest with TestDispatcher to control virtual time, avoiding flaky tests by skipping delays and verifying state flows and cancellation logic execute synchronously.

Yes, you can use CoroutineExceptionHandler for error handling in Android ViewModelScope to catch uncaught exceptions, but for recoverable errors you should use try-catch within coroutine builders.

Use StateFlow for UI state requiring a single updated value exposed to collectors, and SharedFlow for events or transient updates without replaying initial values back to new subscribers.