- Home /
Addressables: LocalLoadPath groups are not updated after "Update a previous build"
Hi all,
One of my addressable group is set a "local", so it is bundled with the application. It also has a "Content Update Restriction" schema that "Can Change Post Release". My other groups are "remote".
After the application is deployed: modify the local group content and "Update a previous build". It won't generate an updated local group bundle in the RemoteBuildPath, and the catalog JSON file still targets the local group that was bundled when the app was packaged. Then this local group cannot really change post release.
A workaround: (temporarily?) change the build path and load path to "remote".
I wonder if it's a bug or not. - it is because it does not update what should be updated - it is maybe on purpose: if another app version is packaged (with the same addressables_content_state.bin), it should bundle this updated local group, not looking for it on remote. So switch automatically on a "remote" bundle in the catalog may be wrong.
Did you find a solution? We are still struggling with this, as I mentioned in my own thread here: https://forum.unity.com/threads/one-project-multiple-apps-x_x.1045120/
Not really, still working with the workaround.
Your answer

Follow this Question
Related Questions
Unity fails to include .bundle for native code plugin when building Intel Mac player. 0 Answers
fail build ScriptableObject into bundle 0 Answers
Unity iPhone Bundle Identifier has not been set up correctly 0 Answers
Addressables Update a Previous Build does nothing on build 0 Answers
Can asset bundled scenes contain original tags which can be read when downloaded? 1 Answer