Addressables included in build not working after upgrading package

Hi everyone,

I'm currently working on a project where there are a lot of addressables included in the build. Everything was working fine until I upgraded the Addressables package to the latest version (1.16.16).

This is the error I'm getting:
Exception encountered in operation Resource<IAssetBundleResource>(StandaloneWindows64\config1_assets_addressablesscenarioindex.asset.bundle), status=Failed, result= : Invalid path in AssetBundleProvider: 'Library/com.unity.addressables/aa/Windows/StandaloneWindows64\config1_assets_addressablesscenarioindex.asset.bundle'


What I noticed is that the path contains a folder that exists in the project, but not in the build:
Library/com.unity.addressables/aa/Windows/StandaloneWindows64\config1_assets_addressablesscenarioindex.asset.bundle

I opened and old catalog of a build that was working correctly and I couldn't find any single reference to "Library". This is the catalog comparison for the same addressable in the old and the new build:


Old build (was working)
"{UnityEngine.AddressableAssets.Addressables.RuntimePath}/StandaloneWindows64/audio5_assets_en-gb/phone/cardio-doesntsoundscardiac_01.wav.bundle"

New build (not working)
"Library/com.unity.addressables/aa/Windows/StandaloneWindows64\\audio5_assets_en-gb/phone/cardio-doesntsoundscardiac_01.wav.bundle"


This is the profile that I've always used, nothing has changed. Why the catalog has replaced the variable {UnityEngine.AddressableAssets.Addressables.RuntimePath} with the Library path?




Thanks in advance!
Cheers

 

Same Problem .But 1.16.15 is OK.Because Unity give developer a bunch of S***!!!!

 

I have this bug too.

 

Thanks a lot!!! 1.16.15 seems to fix the problem for me.

 

I'm also experiencing this bug. I mean, I love Unity, but since the New Year, such bugs seem to appear much more often than ever. Please do test your releases Unity! Some of us can't wait weeks for fixes

 

Thanks, 1.16.15 fixed it for me.

The error I was getting:
After I upgraded Unity to a more recent LTS (2019.4.18f1) the started crashing with "InvalidCastException: Specified cast is not valid." when the preprocess script tried to build addressables. Then I tried upgrading addressables to 1.16.16 and that solved the build issue, but the resulting apps crashed at start due to missing localization bundle:

Exception encountered in operation Resource<IAssetBundleResource>(localization-locales_assets_all.bundle), status=Failed, result= : Invalid path in AssetBundleProvider: 'Library/com.unity.addressables/aa/Android/Android/localization-locales_assets_all.bundle'.

Annoyingly, it worked fine in the Editor, using play mode script “Use exsisting build (requires built groups)” but crashed the build

 

The error happens in BuildScriptPackedMode.cs

Code (CSharp):

1. internal void AddPostCatalogUpdatesInternal(....)
2. {
3. ...
4.                     if (dataEntry != null)
5.                     {
6.                         dataEntry.InternalId = bundleNameWithoutHash;
7.                     }
8. ...
9. }

Quick fix

Code (CSharp):

1. dataEntry.InternalId = StripHashFromBundleLocation(dataEntry.InternalId);

 

same here with unity 2021.2.18.
the default local group is not loading anymore after updating and replacing on server.

but I just found that for this group "can change after release" was selected, which makes no sense, since it is included in the build.
So I will change that now and test.

 

yes .... it has to be "Cannot change post release" for local files that are included in the build. Which seems obvious to me. I wonder why this option is there at the first place???