localization doesn't work in Webgl

Unity Engine
, ,
1

Hi everyone and sorry for the bad english(from a country where English is not the native language
few days ago i import Localization system in my Webgl Project, and its Localization system is v1.0.5,but when i update Localization system to v1.5.1, it’s suddenly doesn’t work at Webgl, and i got error at console:

UnityEngine.AddressableAssets.InvalidKeyException: Exception of type ‘UnityEngine.AddressableAssets.InvalidKeyException’ was thrown. No Location found for Key=Locale

No Locales were available. Did you build the Addressables?
The following (3) IStartupLocaleSelectors were used:
UnityEngine.Localization.Settings.CommandLineLocaleSelector
UnityEngine.Localization.Settings.SystemLocaleSelector
UnityEngine.Localization.Settings.SpecificLocaleSelector

System.Exception: SelectedLocale is null. Database could not get table.

i’m pretty sure i already build addressables groups and put bundle file at right place,it’s anything else i can do?

Unity version:2022.1.4f1
Localization version:1.5.1
Addressables version:1.21.9

2

Hi,
Could you please file a bug report?

3

just send it ,its https://unity3d.atlassian.net/servicedesk/customer/portal/2/IN-72046 thanks for your help

4

This is the same bug as here: Localization 1.5.1 + Unity 2022.3.22 and WebGL
The error is different, but if you delete the Library and Addressables folder of the project and rebuild you will end up with the error I described in my thread.

5

I have seen your post before I submitted the bug report,thought it wasn’t the same bug haha,thanks for your help.

6

The bug is now confirmed Unity Issue Tracker - System.UriFormatException is thrown when building the Localization "Preloading Screen Example" in WebGL

7

Any news on this? I’m having this issue on Unity 6 with localization 1.53 which ia oreventing my game from veing shiped into WebGL environments.

8

Unity 6 didnt have the issue that this bug describes, it was isolated to 2022.3 and fixed in 2022.3.25f1.
Could you please share your logfile with the errors you are getting?

9

The issue was that at some point I changed the compression method from l4z to lzma, That fixed the issue