Quick answer: Unity Addressables content update built but clients still load old assets? Either the remote catalog URL is stale, the cache wasn’t cleared, or update build skipped your group — check build remote catalog plus group’s Update Restriction.
Players downloaded a content update but the new gun mesh doesn’t appear. The Addressables loader is still hitting cached bundles with the previous hash.
Build the Remote Catalog
The content update must regenerate the remote catalog. In the Addressables Groups window → Update a Previous Build — not Build → New Build, which rewrites the base catalog.
Group Update Restrictions
Each group has an Update Restriction. Cannot Change Post Release means the group is skipped — any changes go into a new remote-static or remote-dynamic group instead. Set it correctly for your asset lifecycle.
Clear the Cache
Addressables.ClearDependencyCacheAsync(key);For affected keys after a hash change. Or wipe the entire bundle cache via Caching.ClearCache() during testing.
Catalog URL Stability
The remote catalog URL must be stable across releases — clients fetch it on load. A versioned URL only works if you also ship the new URL in the app.
Verifying
Run a fresh client after the update: the new content downloads, the loader resolves new hashes, and gameplay shows the updated asset.
“Content updates need Update a Previous Build, the right Update Restriction, and a stable catalog URL.”
Tag your content-update builds in git with the catalog hash — debugging stale-content reports becomes a five-minute job.