kotlin-concurrency-expert

Kotlin coroutines cause Android lifecycle leaks and ANRs when scopes and dispatchers are misused. Analyzing your codebase identifies unsafe patterns like GlobalScope usage, replacing them with lifecycle-aware scopes to ensure proper cancellation and thread safety.

To replace GlobalScope with viewModelScope in Android, refactor your coroutine launching to use lifecycle-bound scopes. This enforces structured concurrency, ensuring coroutines cancel automatically when the ViewModel clears, preventing UI responsiveness issues.

The best way to encapsulate MutableStateFlow in Kotlin Android is to expose immutable StateFlow externally while mutating private MutableStateFlow internally. This pattern secures thread safety and prevents external lifecycle components from emitting unauthorized state changes.

Use repeatOnLifecycle for Android coroutines to safely collect flows from Activities or Fragments. This lifecycle-aware function suspends and restarts collection based on lifecycle states, preventing background emissions and reducing unnecessary battery or processing drain.

Yes, you can inject testable Dispatchers in Android coroutine projects. By abstracting Dispatchers through dependency injection rather than hard-coding them, you gain reliable testing capabilities and ensure structured concurrency across your ViewModel and repository layers.

You should not use GlobalScope in Kotlin Android coroutines when operations are tied to UI or business logic lifecycles. GlobalScope outlives components causing leaks; use viewModelScope or lifecycleScope to guarantee proper cancellation and thread safety.