Update content and catalog on remote server

So after we already ship our binary build we want to update some remote contents . We choose Build->Update a Previous Build and uploaded new asset bundles and catalog has and .json to remote server(override older files) . But when we download any asset on the build we already shipped we get error . Do we need to ship a new binary build???

 

No, it does work that way, at least in my own testing. I'm not entirely sure on the details and the correct order, however. The order of the builds could make a difference, please let me know if anyone knows a definite answer. My observation: I build groups, then the player, publish both to server, then build new groups, update groups on server and everything works. If I build the player, then build groups, publish on server and then try to update a previous build it fails. I think its important that the generate .bin file is of the right version, but it's all not too clearly documented, I feel.

 

Our build order so far is like this: build groups->build player->ship both of them->build for update->upload new updated assets and catalog to overwrite old assets . But when we download new assets in old player they all failed after download progress completed . When build for update we already chosen old .bin file and the catalog generated after build for update have the same name as old one .

 

Also interested in this. Starting to use Addressables for the first time and having a definitive answer on the build/release process for remotes would be very useful. Plus any potential pitfalls (like if I do a full build of the groups when the game is live, what does that do the the existing updated groups etc)