Bug "AddressableAssets.InvalidKeyException" after update to 1.14.2

Upgrading Addressables from 1.13.1 to 1.14.2 (2018.4.22f1) broke our game and loading no longer works in the editor. Unity displays the following error message:

Code (CSharp):

1. Exception encountered in operation CompletedOperation, status=Failed, result=UnityEngine.ResourceManagement.ResourceProviders.SceneInstance : Exception of type 'UnityEngine.AddressableAssets.InvalidKeyException' was thrown., Key=8fee809d8b6a25342bb9b513a1f8aada, Type=UnityEngine.ResourceManagement.ResourceProviders.SceneInstance
2. UnityEngine.AddressableAssets.Addressables:LoadSceneAsync(Object, LoadSceneMode, Boolean, Int32)
3. MyCompany.Framework.<LoadCoroutine>d__22:MoveNext() (at assets/plugins/MyCompany_framework/Loading.cs:275)
4. UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) (at C:/buildslave/unity/build/Runtime/Export/Coroutines.cs:17)

The Android build seems to work though.

I'm using the "Use Asset Database" play mode script option in the editor. Downgrading to 1.13.1 gets rid of the error.

 

It seems (in our case) addressables added to groups by folder no longer work when "Use Asset Database" is enabled. If you do a build and swap over to "Use Existing Build" things begin loading again in the editor.

 

Hm, I wonder if this has anything to do with the fix to an issue I reported, where Enter Play Mode time went up from 5-6 seconds to about a minute on our project, spent scanning child items. It was fixed on 1.14.2.

 

We're seeing the same thing @KyleOlsen - Addressables directly added to the groups load in "Use Asset Database" mode, but ones added implicitly via folders do not (with the InvalidKeyException error). Both load properly in "Simulate Groups".

 

Seeing the same issue when calling Addressables.GetDownloadSizeAsync with a list of keys returned by
Addressables.InitializeAsync()

 

FWIW this bug is actually preventing our team from updating from 2019.4.6 to Unity 2019.4.9 (we were unable to upgrade to 7 and 8 due to the Android black screen bug).

Our game started freezing on device on upgrading to Unity 2019.4.9 with Addressables 1.13.1. I found the freeze was happening on a line about loading an asset bundle asynchronously. On 1.14.1 the freeze no longer happens, but slows down our team's workflow significantly as we'd have to work in "Simulate Groups" mode.

 

GetDownloadSizeAsync still throws an exception when passing it the keys returned by Addressables.InitializeAsync(), using Addressables 1.15.1

 

I just figured it was related because the issue didn't exist in 1.13.1, it only occurs when using the Play Mode Script, 'Use Asset Database' and it relates to directories marked as 'addressable'.

InitializeAsync returns an IResourceLocator which itself contains an IEnumerable<object>. The following code:

Code (CSharp):

1. Addressables.InitializeAsync().Completed += locatorHandle => {
2.     if (locatorHandle.Status == AsyncOperationStatus.Succeeded) {
3.         Addressables.GetDownloadSizeAsync(locatorHandle.Result.Keys).Completed += downloadSizeHandle => {
4.             if (downloadSizeHandle.Status == AsyncOperationStatus.Succeeded) {
5.                 // Success download size is downloadSizeHandle.Result
6.             }
7.         };
8.     }
9. };

Emits the following exception:

When

fonts.latin

is a folder marked as addressable:



This is essentially (stripped down) the process we go through in order to have the player download all required bundles on first launch for our game. After grabbing the download size and informing the user the amount they need to download, we pass the keys on to Addressables.DownloadDependenciesAsync. If there's a better way to 'Download everything' please do tell.

For what it's worth, this is super easy to work around - we obviously don't need to download anything when running in Use Asset Database mode, so this chunk of code can just be skipped. But in 1.13.1 we didn't require this conditional. It's handy to have each Play Mode Script behave the same under identical API calls.

Thanks

 

If Keys was empty there would be no InvalidKey exception.

 

Yep, locatorHandle.Result.Keys.Count() is very much > 0 when runnung in Use Asset Database mode

 

I am having this issue when trying to load all assets inside an addressable folder by using a label.

Is my only option to make this work to downgrade to an older version of addressables?

Edit: Nevermind, I had the same issue as described here: https://forum.unity.com/threads/get...hows-on-addressables-resourcelocators.983436/

 

I got same error message. But my key was address.
I foud file extension may be different in catalog file. Some file extensions are in uppercase and some in lowercase. Such as '.Prefab' and '.prefab'.
It will leads to the inability to find the correct key through the address.
I think this is a bug