kotlin-concurrency-expert

To fix Kotlin coroutine leaks in Android ViewModel and Fragment lifecycles, replace GlobalScope with lifecycle-aware scopes like viewModelScope and lifecycleScope to ensure structured concurrency and automatic cancellation upon component destruction.

The best way to replace GlobalScope usage for structured concurrency is to adopt lifecycle-aware scopes such as viewModelScope or lifecycleScope, ensuring that coroutine jobs are properly scoped and canceled to prevent memory leaks.

To safely collect StateFlow in Android Fragments, use repeatOnLifecycle to configure the flow collection within the appropriate lifecycle state, ensuring thread safety and preventing crashes when the view becomes inactive.

You should inject dispatchers in Kotlin coroutines to improve Android testability by allowing you to easily swap execution threads during unit testing, ensuring deterministic behavior and verifying structured concurrency without relying on real asynchronous execution.

Yes, this skill can audit an entire Android module's coroutine usage by analyzing lifecycle handling, scope management, and thread safety, returning a concrete remediation plan to enforce best practices across ViewModel and Activity components.