Changing the Bundle Naming requires new fresh Bundle Build?

Unity Engine
1

Hi.

Previously, the Bundle Naming of every addressable group was set to “Filename”, then I make a new build (Build > New Build > Default Build Script), upload the new bundles to cloud storage and check the download. It works.

Now I select all addressable groups and set the Bundle Naming to “Append hash to Filename”, then I go to Build > Update a previous build. After build success, I delete all bundles in cloud storage and upload new bundles to cloud storage and again clear cache and check the download, then I get exception errors saying “file 404 Not Found”

Exception encountered in operation Dependencies - Chain<IList`1,IList`1>: ChainOperation of Type: System.Collections.Generic.IList`1[UnityEngine.ResourceManagement.ResourceProviders.IAssetBundleResource] failed because dependent operation failed
RemoteAssetBundleProvider unable to load from url https://storage.googleapis.com/maujflix-testing-bucket/Android/udaan_images_assets_all.bundle, result='HTTP/1.1 404 Not Found'.

Now this time, I go to Build > New Build > Default Build Script, delete all bundles in cloud storage and upload the new ones and the download works.

TLDR:

  1. Change bundle naming to “Filename” of every group
  2. Build (Build > New Build > Default Build Script) and upload to cloud storage
  3. Check download - Works!
  4. Change bundle naming to “Append hash to Filename” of every group
  5. Build (Build > Update a previous build)
  6. Upload bundles to cloud storage
  7. Check download - Failed! (404 Not found error)
  8. Build (Build > New Build > Default Build Script) and upload to cloud storage
  9. Check download - Works!

So my question is changing the Bundle Naming, requires a new fresh build? And Content workflow won’t work?

My addressables version: 1.8.5
Unity version: 2019.3.15f1

2

@Spectra_7 Hi there, unfortunately yes, this is the case. If you wish to change the bundle naming you’ll need to do a new build.

This is because if you change the bundle naming when you do a content update, the old client will have no means of knowing which of the new bundles corresponded to which of the original bundles. That said, we’ve made plenty of improvements and bug fixes to the content update workflow in general in newer versions of addressables, so if you ever run into further problems (or just want to avoid running into more problems in the first place!) I would recommend updating to one of the newer versions of the package.