Hi
Here is my addressable setting
The addressable does not update the catalog from remote.
It always loading and using catalog from jar:file://data/app/com.test.addressable/base.apk
Is someone also have the same problem and solve it?
Please help me how to fix the problem?
Thanks.
Hey @jiahongzeng what Build and Load path does your Addressable Group use? The Settings object will show what it is set to but the Group itself drives where the content is built and how it is loaded.
Thanks for the reply.
Here is my group setting
Is there any wrong setting about it?
I’m curious about your Load Path. Is it just that Addressables won’t download it? If you use UnityWebRequest and point it to that same location does it download the file?
Also are you using the Hosting Service that Addressables provides?
Hi.
1 . The load path is my ftp server.I am sure It will load file from the path.
2 . I am not use the Hosting Service.
I have tried to modify the settings.json in Library\com.unity.addressables\StreamingAssetsCopy\aa\Android
I change
"m_Keys":["AddressablesMainContentCatalog"],"m_InternalId":"{UnityEngine.AddressableAssets.Addressables.RuntimePath}/catalog.json"
into
"m_Keys":["AddressablesMainContentCatalog"],"m_InternalId":"http://(the ip of my ftp)/Android/catalog.json"
After that I rebuild the apk and install,the app will get the catalog from my ftp.
When I upload the update bundle file and reopen app,it can get the new bundle file.
This is what I found.
Thanks.
Not yet unfortunately. The behavior your describing is very odd to me. The fact it works after a bundle update puzzles me a bit. Will you file a bug with Unity and post the case number here? It’ll help me keep track of this.
Hey, not yet. I’m planning on bringing this issue into our next sprint to look at.
Thank you for the replying.
Thanks for this!
Okay! So this is how I am working with Addressables now. (using Unity 2019.2, Addressables v 1.5)
Build your remote bundle using “New Build” (make sure you check “build remote catalog” and “content can change post release”.) and deploy to your remote server.
(Important!) Do as mentioned by @jiahongzeng ,
(i.e. modify the settings.json in “Library\com.unity.addressables\StreamingAssetsCopy\aa\Android”) Then,
Build your app (android) and deploy/install wherever you want.
Update your remote content group however you want using “Update existing build”.
Voila! You will get updated content from your already installed apk. 
ps: I know many of you already know this, but I struggled and in case someone else does. Big thank you jiahongzeng!
@mango_khan Is this still working for you. I’m worry about the .gitignore often include the content of library directory so the workaround of this really not reliable if working with multiple people 
Oh hey everyone! How are you folks doing? Great, I hope!
So… it’s 2022, the great and beyond future and Addressables still doesn’t update my content.
Hooray!
Which is great, I mean the feature isin’t supposed to work right?
So here is the thing… I tried what @jiahongzeng recommended, which is editing the settings.json over at “Library\com.unity.addressables\StreamingAssetsCopy\aa\Android” and change the catalog.json address to the one in my Google Cloud bucket…
But here is the thing, whenever I do a new build OR build update, it doesn’t matter! the settings is rewritten to “{UnityEngine.AddressableAssets.Addressables.RuntimePath}/catalog.json” and when I open my app, guess what? No updates!
Even if I completly delete the content from my bucket, still shows up the old content on the app!
I’m probably making something wrong or Addressables simply hates me.
I attached my Addressables Settings if anyone is interested
Checking “Unique Bundles IDS” in Addressables Settings did it for me