unity-addressables-design

Use Addressables.LoadAssetAsync<T>(key) and await handle.Task, then check Status before reading Result. Always release the handle with Addressables.Release(handle) when finished, or the AssetBundle stays in memory indefinitely.

Replace every non-Async method (LoadAsset, Instantiate, LoadScene, Initialize) with its Async counterpart, since all obsolete variants were removed in 2.9.1. Also convert IList<object> multi-key arguments to IEnumerable and remove LegacyResourcesLocator and diagnostic API references.

This happens when a handle is released twice or used after release, such as mixing Addressables.Release(handle) with AssetReference.ReleaseAsset() on the same load. Use exactly one release path per load call.

No, WaitForCompletion is unsupported on WebGL and throws because the JS backend cannot synchronously pump async operations. Use await handle.Task or the Completed event instead, and guard any WaitForCompletion usage with platform conditionals.

SceneReleaseMode is a new enum in 2.9.1 controlling whether the scene's AssetBundle releases when the scene unloads. The default ReleaseSceneWhenSceneUnloaded matches 1.22.3 behavior; OnlyReleaseSceneOnHandleRelease requires a manual Addressables.Release call.

Call CheckForCatalogUpdates first to get only the stale catalog IDs, then pass that list to UpdateCatalogs. Skipping the check re-downloads every registered catalog on each launch even when nothing changed.