Addressables not loading content update from remote server properly

Question

I am able to retrieve the content of my project on the first run of the app, however, after I update the contents of my Addressables, my built app (apk) does not reflect the changes.

My guess was it was loading from a local cache of some sort, so I deleted the catalogs and bundles from my server and ran the app… and what do you know, I was right. the assets were still being loaded even of there was nothing in my bucket… meaning the addressable system was loading a local cahe

1. I have checked Build remote catalog in the settings
2. I have unchecked Use Asset Bundle cache from the group settings
3. the group settings is can change post release

Any solutions for this?

I’ve been banging my head for almost a week and the docs are not helping.

Propellant

@Propellant Facing the same issue. Did you guys find a solution to this?

– Starryeyed

Answer 1

@Propellant Facing the same issue. Did you ever find a solution to this?

Might

Answer 2

@Propellant Facing the same issue. Did you guys find a solution to this?

Starryeyed

Answer 3

Hey… so… it’s 2022 and still isn’t possible to update content remotly after building and app. So i’m guessing Unity just dropped the feature?

I’m using Unity 2020.3
Addressables is 1.20.3

Costello

Answer 4

So… It is almost 2024. There is still no good explanation in the internet about how to use Addressables properly with remote assets, thats you gonna update. I’m not sure it is still a bug, but how to make it works is a secret, that, probably, even Addressables developers don’t know how to solve.

P.S. If you are looking for solution to manage your remote assets, it’s much more easier develop own assets management system, based on AssetBundle technology. For now. Who knows… maybe in 10-20 years Unity, finally, will make something good with Addressables.

Tijuana

Answer 5

Hey, so I have a couple of suggestions that might help. I’ll post some specifics below, but here’s the manual page on content updates Content update builds | Addressables | 1.21.20

1. Make sure you’re going through the Update a Previous Build workflow. If you’re doing fresh builds every time, the default time stamp on the catalog is going to change. Since the name of the initial catalog is built into your runtime settings, it’s not going to know where to check.

2. In that same vein, you could use the Player Version Override setting to hardcode a version so that you’re not reliant on the timestamp. Just make sure you update this if needed. You can find more info about it here Addressable Asset Settings reference | Addressables | 1.21.20
   To note, in newer versions of Addressables we actually use the AssetBundle Version as the player version override when building the catalog. [UnityEditor.PlayerSettings.bundleVersion]

3. Also when you’re doing a build, make sure you’re uploading the new remote catalog AND the new .hash file that gets built alongside that catalog. The hash file is how we determine if your catalog has new information so we can download it.

Hope this helps!

Shepard