kotlin-coroutines-skill

To fix Kotlin coroutines cancellation bugs and scope leaks, apply structured concurrency by choosing the right scope and preserving parent-child cancellation behavior. This prevents orphaned background work when the parent scope clears.

Making Kotlin suspend functions main-safe requires dispatcher injection to ensure blocking work runs on the correct background thread. This prevents blocking the main thread and makes suspend functions safe to call directly from Android UI code.

Writing deterministic Kotlin coroutines and Flow tests requires replacing real-time delays with virtual-time test patterns. This approach controls the dispatcher scheduler, ensuring tests run instantly and reliably without flaky timing dependencies.

Yes, the approach supports reviewing Kotlin Multiplatform (KMP) shared modules for concurrency safety. It analyzes shared KMP code to catch dispatcher misuse, Flow collection mistakes, and cancellation bugs across Android and backend concurrency scenarios.

Kotlin Flow collection leaks during Android lifecycle changes occur when collection is not lifecycle-aware. Implementing lifecycle-aware Flow collection patterns ensures state handling and event delivery pause and cancel correctly when the view destroys.

You should not use GlobalScope for Kotlin coroutines when work needs to be tied to a specific lifecycle or caller. Using structured concurrency with custom scopes prevents uncancelable leaks and ensures operations fail predictably.