kotlin-concurrency-expert

To fix Kotlin Coroutines ANR and leaks, diagnose improper scope usage and enforce structured concurrency. Apply minimal, safe fixes using lifecycle-aware scopes like viewModelScope to ensure proper cancellation and thread safety across MVVM architectures.

Implement lifecycle-safe coroutine collection using repeatOnLifecycle with lifecycleScope. This prescribed pattern prevents crashes and ensures multi-threaded data flows only emit when the Android lifecycle component is at least started, suspending collection appropriately on stop.

Structured concurrency in Kotlin enforces parent-child coroutine hierarchies to prevent race conditions and leaks. By binding coroutines to specific scopes like lifecycleScope, it guarantees cancellation propagation and safe dispatcher handling across multi-threaded data flows.

Yes, this approach works across Android codebases using MVVM architectures and lifecycle components. It applies minimal behavioral changes to diagnose coroutine issues and provides migration guidance to modern best practices without requiring a full rewrite.

Kotlin Coroutines cause crashes on activity destruction due to improper scope usage and lack of lifecycle-aware collection. Remediate this by migrating unsafe scopes to viewModelScope and applying structured concurrency to handle cancellation safely.