Upgrading to addressables@1.21.9 gives error on BuildSettings WebGL

Unity Engine
,
1

Just upgraded to Unity 2022.2.11f and addressables@1.21.9 and I get this error, when the Build is set in the Editor to WebGL. It works fine when the Build Settings are set to Windows/Mac/Linux
Library\PackageCache\com.unity.addressables@1.21.9\Editor\Diagnostics\Profiler\AddressablesProfilerDetailsDataInspector.cs(217,44): error CS0103: The name ‘DownloadWithoutCachingEnabled’ does not exist in the current context.

Any idea what is going on here?

2

Ok guys, this seems really bad that it passed PRs…? This code is on AddressablesProfilerDetailsDataInspector:

#if ENABLE_CACHING
if (!bundleData.CachingEnabled)
m_HelpManager.MakeHelp(ProfilerStrings.DownloadWithoutCaching);
#else
if (bundleData.CachingEnabled)
m_HelpManager.MakeHelp(DownloadWithoutCachingEnabled);
#endif

Notice the line on the #else region??
This is wrong:
m_HelpManager.MakeHelp(DownloadWithoutCachingEnabled);
This is probably what should be there instead?
m_HelpManager.MakeHelp(ProfilerStrings.DownloadWithoutCachingEnabled);

1 Like
3

Came to say exactly this. How did no unit test or build machine catched that glaring bug?

4

Hi all thanks for posting the issue. I’ve created a bug ticket, and the issue will be fixed in the next release (1.21.11).

2 Likes
5

Can you post the bug ticket so we can follow it please @pillakirsten ?

6

It might take a while for the public link to work, but here it is: https://issuetracker.unity3d.com/product/unity/issues/guid/ADDR-3341

7

So I updated Addressables and I’m now in this pickle. Tried removing Addressables and installing 1.21.8, but I still get the compile error. Any tips for a fix/workaround @pillakirsten ? Thanks

8

Yes there is. You can copy the package (com.unity.addressables@1.21.9) from the Library/PackageCache to the Packages folder. Rebuild. Click on the error to go to the code where the issue is at (which is now in the packages folder so it can be edited) Fix the error. You are good to go !

2 Likes
9

Yes creating a custom copy of the package is the best workaround at the moment.

1 Like
10

Updating to com.unity.addressables@1.21.12 had this error fixed.