unity-unitask-design

To prevent double-await crashes in Unity UniTask async code, enforce struct single-await semantics and use Preserve() when you need to await the same UniTask instance multiple times. This avoids invalid struct re-evaluation and ensures safe async correctness.

Use Forget() in UniTask when you need fire-and-forget execution without blocking the calling sequence, while understanding that unhandled exceptions flow through UniTaskScheduler. Awaiting is required when the caller must suspend until the async operation completes for proper operational lifecycle management.

Correct Unity UniTask cancellation token propagation involves using GetCancellationTokenOnDestroy for component lifecycle tracking and AttachExternalCancellation to link external tokens. Proper propagation ensures async operations terminate cleanly and prevents leak-prone subscriptions when GameObjects are destroyed.

PlayerLoopTiming determines the exact Unity lifecycle slot where UniTask async continuations execute, such as Update or LateUpdate. Selecting the correct timing slot ensures async operations synchronize properly with the Unity frame loop and avoid execution order conflicts.

Convert Unity coroutines and enumerators to UniTask using built-in conversion APIs, and wrap AsyncOperations with AsyncOperation.ToUniTask to enable direct awaiting. This composable architecture allows seamless interoperability between traditional Unity async patterns and UniTask workflows.

When reviewing Unity UniTask code in a PR, check for tracker issues, undisposed subscription leaks, and improper enumerator termination. Consolidate these pitfall patterns into an actionable checklist to ensure cancellation requirements are met and async correctness is maintained.