unity-async

Use Unity coroutines for short sequential animations or delayed logic, and Update for continuous simulation or input polling. Coroutines tie execution to MonoBehaviour lifecycle, making them suitable for time-bound sequences rather than continuous per-frame tracking.

Handle UniTask cancellation by defining lifecycle ownership and maintaining subscribe/unsubscribe symmetry across OnEnable, OnDisable, and OnDestroy. Assign cancellation tokens to specific MonoBehaviours and dispose them properly to prevent leaking subscriptions.

You do not need UniTask if native Unity coroutines suffice for your short sequential tasks. UniTask is an optional dependency recommended for projects requiring complex task scheduling, hot-path performance optimizations, or advanced cancellation strategies beyond coroutine capabilities.

The best way to schedule delayed work in Unity without leaking subscriptions is using timer-based scheduling with strict IDisposable cleanup. Ensure subscription symmetry by unsubscribing during the corresponding MonoBehaviour lifecycle event like OnDisable.

Your Unity async pattern causes performance issues in the hot-path Update loop due to improper scheduling or missing caching. Choose event-driven work over per-frame polling and cache references to avoid garbage generation and unnecessary computation during continuous execution.