Disable Catalog Update on Startup = Not updating addressable changes

Enabling “Disable Catalog Update on Startup” then make some changes in remote bundles and upload them to the server = previous builds do not update their content.

  • Addressables.GetDownloadSize gives 0.

Is there something I’m missing, is there the need for an extra step that’s not on the documentation?

So you either accept the fact that addressables will always auto-update the bundles or just don’t use it?

Did you call “CheckForCatalogUpdates” and “UpdateCatalogs” before calling “GetDownloadSize”?

if I got it right. the GetDownloadSize only checks the assets/assetbundles that will be downloaded, this does not include any catalog updates.

  • Calling “CheckForCatalogUpdates” check if there is any update. This downloads the hash file and compares it with the local one. Returning a list of catalogs that need to be updated.

  • UpdateCatalogs will update the catalogs

  • after which GetDownloadSizeAsync should give you the size of the update

  • and calling DownloadDependenciesAsync will then save them on your device.

1 Like

Apparently “CheckForCatalogUpdates” and “UpdateCatalogs” don’t work, they just exist.

I will try this out…I dont understand where the ‘catalog’ is stored unless it’s in the remote path…the new build doesn’t have anything in it except bundles sooo not sure.

1 Like

posted: