kotlin-concurrency-expert

Fix coroutine leaks and ANR by enforcing structured concurrency and lifecycle safety in your Android code. This involves replacing GlobalScope with lifecycle-aware scopes like viewModelScope, injecting dispatchers to move work off the Main thread, and ensuring proper cancellation handling.

GlobalScope causes lifecycle bugs because it creates coroutines that outlive their calling component, leading to memory leaks and crashes. Replacing GlobalScope with lifecycle-aware scopes like lifecycleScope or viewModelScope ensures coroutines are automatically cancelled when the associated lifecycle is destroyed.

Review Kotlin code for improper coroutine usage by triaging for GlobalScope instances, missing cancellation handling, and incorrect Dispatchers. Propose a minimal patch set encapsulating mutable state and injecting dispatchers for testability to enforce structured concurrency.

Yes, this approach works for ViewModel-heavy Android projects using coroutines. It directly targets lifecycle safety in viewModelScope usage, preventing ANR by moving work off the Main thread and ensuring proper scope handling during configuration changes.

Inject Dispatchers for testability by passing them as dependencies rather than hardcoding them. This encapsulates mutable state and allows swapping real dispatchers with test dispatchers during unit testing, ensuring structured concurrency without side effects.

Handle coroutine cancellation in Android lifecycle scopes whenever the associated lifecycle is destroyed, such as when a ViewModel is cleared. Robust cancellation handling prevents leaks and ensures background tasks do not update destroyed UI components.