Problem with content update a local static group

P.s: title better named “Local static group cannot load when content update an isolated remote group”

Hi all,

I am using Unity 2018.4.7f1 with Addressable@1.2.4. We currently having lots of problem with content updating the game, mainly due to this problem (on Android):

Exception encountered in operation Resource<IAssetBundleResource>(splashscreen_assets_all_8005be38e33d354ebce71e5dfdc0cfd2.bundle): RemoteAssetBundleProvider unable to load from url jar:file:///data/app/com.autumninteractive.myrummy-hERRbbvwFw6qrZf1KmmO_A==/base.apk!/assets/aa/Android/Android/splashscreen_assets_all_8005be38e33d354ebce71e5dfdc0cfd2.bundle, result='HTTP/1.1 404 Not Found'.

(Check android_error.txt file attached for full stack trace)

The “splash screen” is a local static group. However, we only change a scriptable object on a remote group that has no relation with that group. Check for content update will not detect any changes on the groups.

I managed to reproduce the problem on a fresh project (use Addressable 1.4.0 instead of 1.2.4). Simply setup a local static group. Build content update. Build the game binary. Then try do a content update (Check for content update → Apply to get a new Content update group, then Update previous build). I will have the similar problem:

Exception encountered in operation Resource<IAssetBundleResource>(localstatic_assets_all_c36a8e484bde2671cafb3ad047495e2e.bundle): Invalid path in AssetBundleProvider: '/Users/ngtrhieu/repositories/Test Addressable/Builds/v0.1.dev.s3.app/Contents/Resources/Data/StreamingAssets/aa/OSX/StandaloneOSX/localstatic_assets_all_c36a8e484bde2671cafb3ad047495e2e.bundle'.

(Check reproduce_error.txt file attached for full stack trace)

What might be the cause of this?

5290077–530865–reproduce_error.txt (8.56 KB)
5290077–530868–android_error.txt (1.34 KB)

1 Like

The repo used to reproduce the bug is here:
https://github.com/ngtrhieu/test-addressable

Please submit this as a case in Unity’s bug reporting tool if you haven’t so the Addressable devs can see/fix it.

2 Likes

You can link to the bug report here and I can also take a look. Thanks!

Does the issue persist on 1.5.0?