Updating non-static remote assets with remote catalog

Unity Engine
1

We’re currently attempting to figure out our update process for the remote addressables we’ve recently implemented.

We have a number of addressable groups, all of which are hosted remotely and non-static, and use hashes in their bundle names. We have a remote catalog hosted on the same service as the assets.

It is my understanding that to update these assets, we can simply:

  1. Build player content
  2. Upload the new asset bundle files and remote catalog (+ hash) to the remote hosting service.

and existing clients (upon restart, at least) will automatically refer to this new catalog when looking for assets, and update any old bundles as required.

However, we’ve run into some issues with this, where assets cannot be found - even though they are clearly able to communicate with the remote hosting service.

Is there something wrong with the above update process? Again, all assets are remote (as is the catalog), and non-static.

Thanks in advance!

2

I think you want “Build for Content Update” if you have an already distributed build that you want to load updated or additional assets in.

Build Player Content creates a new json catalog file with a new timestamp in the filename, whereas Build for Content Update overwrites the existing one, and I believe distributed builds reference the json file it was built with.

1 Like
3

You are absolutely right - this is the first time I’ve understood any explanation of what that button actually does outside of creating updates for static content. Thanks!