I changed Bundle Naming to “Filename” and disabled Asset Bundle CRC checking because I was getting CRC mismatch errors.
Then, I make a content update and choose “Update a previous build” where all content updates in overwritten in a single file instead of making a new file with new hash.
Finally, I copy the files and overwrite it with files existing in cloud storage.
But when I open my game, it doesn’t download new content update unless I clear cache.
The download uses the contents hash as the cache version. If that hasn’t changed in the catalog then it will fetch it from the cache.
Content update workflow will replace any updated info on bundles that are set to “Cannot change post release” to that of the original release. Which could be why you need to clear your cache?
It is quite confusing and we are doing work to try and make this easier to understand. You kind of need to understand it to use it.
Content update workflow does not actually do anything to groups marked as “Can change post release” The workflow works on “Cannot change post release” content. Anything that “Can” is ignored.
Essentially:
“Can change post release”: don’t need to do anything special with this, it can change already without anything special needed.
“Cannot change post release”: This cannot be changed through any means, most commonly that it is built into the Player build and not downloaded at release time. If we want to change anything in here, we must move it out.
The easiest way to work with this, is to set anything that will be local/included in the Player as “Cannot change post release” and everything remote/downloaded as can change.
Content that has change since the new release that is in a group with “Cannot change post release” must be moved to a group that can change in order for it to be able to be updated. This also includes anything that references it, in order to find it in the new location.