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 all non-Async methods like LoadAsset, Instantiate, and LoadScene with their Async counterparts, since 2.9.1 removed them. Also convert IList<object> multi-key arguments to IEnumerable and remove references to LegacyResourcesLocator and DiagnosticEvent.

This happens when a handle is released twice or used after release. Each load acquires one reference count, so call Release exactly once, and never mix Addressables.Release with AssetReference.ReleaseAsset on the same load.

No, WaitForCompletion is unsupported on WebGL and throws because the JavaScript backend cannot pump synchronous waits. Use await handle.Task or the Completed event instead, guarding any WaitForCompletion calls with platform conditionals.

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

Use LoadAssetAsync plus manual Instantiate when pooling many instances from one bundle load. Use InstantiateAsync when each instance should carry its own handle lifetime, then destroy it with Addressables.ReleaseInstance rather than GameObject.Destroy.