Error when generating addressables with Localization package

This is what I see when generating addressables:
7566604--936655--upload_2021-10-12_17-42-9.png

It seems to be localization package specific as when I remove it addressable generation proceeds as normal.

Any ideas what might be the problem?

Using unity 2020.3.15f2

7566604--936655--upload_2021-10-12_17-42-9.png

There’s not enough info in those error messages to say.
Did you just start using the package or did you upgrade?
Theres some issues with addressables getting corrupted.
Try running the analyzers to see if any problems can be found.

Analyzers found no issues but I figured it out thanks to this topic: Release version of localization tools broke addressables build

Turns out Addressabless 1.19.9 and localization 1.0.3 on unity 2020.3.15f2 or some combination of those causes build path and load path in groups that Localization adds to Addressables to be empty. Those with same error need to manually change to LocalBuildPath and LocalLoadPath on each group as on screen below:

1 Like

The Addressables team just confirmed that this is a known bug caused by a change in 1.18.9 Added path pairs feature that changed the profile variable names (i.e. LocalLoadPath → Local.LoadPath). Any settings objects that still use the old names will run into the mentioned issues. They will have a fix in an upcoming release. For now the above workaround will work.

Im facing this issue on Addressables 1.18.19 (which is the Verified version for 2020.3 LTS right now)
Please provide more info: when fix will be released and in which version?

It should be fixed in the latest addressables release

I’m on 2020.3.35f1 and Addressables 1.19.19 and this still happens. No fix in half a year?

Update: Actually, I see the correct Load/Build path in all of my groups, but the error still shows

You have the same error message? Can you try running the addressables analyzers which can be found in the addressable groups window toolbar.

Hi,
I’m sorry, but I was browsing this thread at the same time and replied here by mistake. The errors are similar.
So it is the same exact error as in that thread (2 errors about empty path “”). I’ve posted there