unity-unitask-design

Call this.GetCancellationTokenOnDestroy() on the MonoBehaviour, GameObject, or Component and pass the token into every async UniTask method in the chain. Plain C# classes lack this extension and must own and dispose their own CancellationTokenSource.

UniTask is a struct wrapping a pooled IUniTaskSource and token; after the first await the source is recycled, so a second await throws InvalidOperationException. Call .Preserve() once to get a memoized copy that supports multiple awaits.

UniTask avoids per-await allocations by using a struct and pooled state machine, making it suited for Unity's frame-driven loop, while Task allocates per operation. Convert between them with AsUniTask() and AsTask() when interoperating with .NET libraries.

No. UniTask.RunOnThreadPool, UniTask.Run, and SwitchToThreadPool throw NotSupportedException on WebGL because the platform is single-threaded. Guard such calls with #if UNITY_WEBGL && !UNITY_EDITOR and fall back to cooperative Yield-based work.

Call request.SendWebRequest().ToUniTask(progress: Progress.Create<float>(...), cancellationToken: ct) and catch UnityWebRequestException for network failures. A plain await on the operation skips progress wiring, cancellation, and typed error handling.

Use UniTask.Yield or NextFrame to back off one frame and Delay with an explicit DelayType (DeltaTime, UnscaledDeltaTime, Realtime) for time-based waits. Delay(0) still pumps through the PlayerLoop, so it is not a same-frame yield.