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 done, or the AssetBundle stays in memory indefinitely.

Addressables 2.9.1 removed all non-Async methods like LoadAsset and Instantiate, replaced IList<object> overloads with IEnumerable, and added SceneReleaseMode for scene loads. LegacyResourcesLocator and diagnostic callback APIs were also removed.

This happens when you use a handle after releasing it, or release the same handle twice. Mixing Addressables.Release(handle) with AssetReference.ReleaseAsset() on the same load also causes double-release exceptions.

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 calls with platform conditionals.

Call CheckForCatalogUpdates first to get stale catalog IDs, then pass that list to UpdateCatalogs with autoCleanBundleCache enabled. Skipping the check re-downloads every catalog each launch, wasting bandwidth.

Unity cannot serialize the open generic AssetReferenceT<T> directly. Use a closed subclass like AssetReferenceGameObject, or define your own subclass of AssetReferenceT<YourType> for custom asset types.