unity config_error ai_generated true

UnityEngine.AddressableAssets: Initialization failed: Content catalog hash mismatch. Expected 'abc123', got 'def456'.

ID: unity/addressables-catalog-hash-mismatch

Also available as: JSON · Markdown · 中文
85%Fix Rate
82%Confidence
1Evidence
2023-11-05First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
1.21.17 active — — —
1.22.0-pre.2 active — — —

Root Cause

The local addressables content catalog hash does not match the remote catalog hash, indicating a stale or corrupted local cache.

generic

中文

本地可寻址内容目录哈希与远程目录哈希不匹配，表示本地缓存已过时或损坏。

Official Documentation

https://docs.unity3d.com/Packages/[email protected]/manual/InitializeAsync.html

Workarounds

  1. 92% success Clear the Addressables cache at runtime: `Caching.ClearCache(); Addressables.InitializeAsync();` 
    Clear the Addressables cache at runtime: `Caching.ClearCache(); Addressables.InitializeAsync();`
  2. 88% success In the Editor, go to Windows > Asset Management > Addressables > Settings and click 'Clean Build' > 'All' to rebuild both local and remote catalogs. 
    In the Editor, go to Windows > Asset Management > Addressables > Settings and click 'Clean Build' > 'All' to rebuild both local and remote catalogs.
  3. 85% success Manually delete the catalog cache folder at `{persistentDataPath}/com.unity.addressables/` then reinitialize. 
    Manually delete the catalog cache folder at `{persistentDataPath}/com.unity.addressables/` then reinitialize.

中文步骤

  1. Clear the Addressables cache at runtime: `Caching.ClearCache(); Addressables.InitializeAsync();`
  2. In the Editor, go to Windows > Asset Management > Addressables > Settings and click 'Clean Build' > 'All' to rebuild both local and remote catalogs.
  3. Manually delete the catalog cache folder at `{persistentDataPath}/com.unity.addressables/` then reinitialize.

Dead Ends

Common approaches that don't work:

  1. 90% fail

    The hash mismatch is between local and remote catalogs; deleting settings removes the entire configuration, not just the cache.

  2. 95% fail

    Addressables uses its own cache in Application.persistentDataPath, not the browser cache; clearing browser cache has no effect.

  3. 60% fail

    Reimporting builds a new local catalog but doesn't update the remote catalog; the mismatch persists if remote hasn't been rebuilt.