Hi,
It appears that local loading dosen’t work with addressable for WebGL builds. (Dosen’t detect those keys).
Is that accurate?
This also cause the com.unity.localization package to not work as it depends on the Locale package.
How does everybody manage that segregation between WebGL vs other builds? Thanks!
This is not working even on build and run
Hi @dan_soqqle Addressables does support WebGL. Local addressable assets are stored in the Application.streamingAssetsPath.
It sounds like you are running into InvalidKeyExceptions, did you build Addressables (in the Addressable Groups window toolbar > Build > New Build) before building the player?
Hi, sorry for delayed reply. Yes i did build it (many many times, otherwise it wouldn’t have worked. However, it worked after migrating to 2021.
And also I updated my com.unity.localization package to the latest (it did not detect Locale). However, it should not impact the other local ones. Actually the one that failed was the scene I included in the build (which usually works when I loadsceneasync) but in this case through WebGL it did not.
Anyway on 2021 I did manage to get this to work locally (however had some issues on unity play, and kind of gave up on unity play, will recheck that shortly)
I’m having the same problem, but I’m already on 2021.3.5f1.
Difference is, other assets work; only scenes don’t load, for ex. giving:
DragonShift.framework.js:3 UnityEngine.AddressableAssets.InvalidKeyException: Exception of type 'UnityEngine.AddressableAssets.InvalidKeyException' was thrown., Key=Assets/_AppGame/DevSetup/Res/DevSetup.unity, Type=System.Object
It works on all other platforms.
More info found. Only this part fails (but, again, not on other platforms):
var locations = await Addressables.LoadResourceLocationsAsync(scenePath, typeof(SceneInstance));
var first = locations[0];
var size = await Addressables.GetDownloadSizeAsync(first); // size shows correctly
await Addressables.DownloadDependenciesAsync(first, autoReleaseHandle: true); // <<< here it fails
I got similar errors.
Do you have the addressables local or remote?
I have one project where everything is loaded from streamingAssets, this works fine.
But the other project loads the bundles from a remote server.
Here I get those errors.
And the system tries to load this: “http://localhost:3000/StreamingAssets/aa/settings.json” which does not happen on windows.
So it seams to me that it does not load the remote catalog, which causes that invalid key exceptions I think.
i have both because i have localization which uses local. i have not upgraded to 2022 though.
But more recently i have not got this error anymore. I do try a combination of turning off and on exceptions and compression which appears to be causing many many issues
But it seems to happen less when i select “perserve uv foldover” and “preserve uv seams”
updates on this? still happens on u2022.1.24f1, latest addressables v1.21.8
@pillakirsten
This happens to me in Unity 2022.3.16f1 and Addressables 1.21.19. I reported it in this thread Can't load addressables local group on WebGL build uploaded to Itch.io and CrazyGames - Unity Engine - Unity Discussions . In that game, I had no problems with localization groups. But now, I do in another game. This is the error I get:
Did anyone solve this?
Ok, I think I’ve fixed it by upgrading Addressables to 1.21.20. Hope this helps.
