I have non-static (Can change post-release) local group and checked the “Build remote catalog” in addressableAssetSetting file. when I change some asset in this group and update the assets build, it creates the local bundle and put the new bundle’s name into the catalog. As far as I realized, I should upload the new catalog to the host and game reach this catalog to get the bundle’s name and assets address.
The problem is that the previous version of the game has a different local asset bundle with a different name and can’t load its own bundle.
How could I prevent this problem?
I think you’re not supposed to have non-static local groups. Instead, set the group to “Cannot Change Post Release”, and when when you want to update, go to Tools > Check for Content Update Restrictions, which automatically moves the changed assets in your local group into a new remote group.
You can then upload that to your remote server, and your build will use that for your updated assets, while still relying on the local group you shipped with it for assets that haven’t changed.