Addressables v2.7.2
I’m having some issues with having both local and remote addressable groups. I’ve recently started working with Unity Localization and all the localization assets are local, but I have a bunch of other groups all set to remote. I can confirm that all the groups are pointing to the proper build and load paths, as well as the build profiles that im using.
However when I build addressables and then make a apk of my project, the local addressables fail to load unless i’ve fully uploaded all the remote addressables to my CDN. I can see in my Library/com.unity.addressables/aa/Android folder that the local addressable were indeed built to that location. The only ways I’ve managed to get the local addressables to work with uploading my remote is to either, delete every remote group so that there are only local addressable groups left, or to make my build profile point remote to the local path to, which isnt really a solution.
I’ve created a fresh project and recreated my setup, and that project seems to have no issues with local addressables working without uploading the remote addressables.
I did notice in the addressables build report that even though both the build profile and local asset groups use the default locations that build location of the local group is the remote path
Any help with this would be greatly appreciated, i’ve been banging my head against the wall for multiple days now.
Hi, so it sounds like you mostly have this setup correctly. The way Addresables works a catalog is meant to be pretty much the complete state of assets in the game, so being able to download the remote catalog is very important.
What I do when developing for Android is use multiple profiles setup in the Addressables profile window. I have a production one and then I have a development one that points at my local machine:
In this case I then go into [PROJECT DIRECTORY]/ServerData/Android and run a one-liner to get an http server:
npx http-server -a 0.0.0.0 -p 8000 -c-1
or
python3 -m http.server
This lets me keep building Asset Bundles and getting updates as I work on my project. Then when I’m happy with what I have I upload them to the remote folder (or more normally I have the CI run the build and upload the results to the remote folder).
I think this just builds remote addressables to my local machine?
I dont think I explained very well lol.
The problem i’m having is that when I have some addressable groups set to remote, and then I have my localization addressable groups set to be local to be built into the app. What ends up happening is the local addressables wont work in the app build unless i’ve uploaded the remote addressables and the device is connected to the internet.
When I do this same set up in a fresh project I get the desired results, where the app build immediatly has access to the local localization addressable groups, even though the remote addressables havent been uploaded/device isnt even connected to the internet.
When I look at the addressable report after building addressables. I see that it shows both local and remote addressables are built to the remote destination, even though the build profile has local addressables setup properly to be built locally.
