unity-addressables-design

To prevent Unity Addressables memory leaks, you must enforce correct AsyncOperationHandle lifetime management by ensuring every handle is explicitly released. This Skill guides you in applying the required release discipline to avoid AssetBundle memory leaks across Unity versions.

The correct Unity Addressables catalog update sequence requires strict CheckForCatalogUpdates followed by UpdateCatalogs ordering, with safe CleanBundleCache timing applied afterward. This Skill enforces that specific sequencing to prevent catalog update and bundle cache failures.

To handle Unity Addressables scene release correctly, you must use SceneReleaseMode in version 2.9.1 and proper activateOnLoad patterns. This Skill guides correct usage to avoid bundle lifetime bugs during LoadSceneAsync and UnloadSceneAsync operations.

A Unity Addressables AssetReference throws a double-release exception when cached-handle release is not differentiated from direct Addressables handle release. This Skill provides rules to differentiate AssetReference release mechanics and prevent double-release exceptions.

Yes, this approach supports Unity Addressables version differences by enforcing version-safe API usage for both 1.22.3 and 2.9.1. It prevents calling non-Async or removed APIs that fail compilation or break behavior between these specific Addressables versions.

Limitations when implementing WebGL-safe async patterns for Unity Addressables include avoiding blocking calls and adhering strictly to async-only APIs. This Skill constrains you to WebGL-safe async patterns to ensure downloading and preloading work correctly on the web platform.