Search Issue Tracker

Fixed

Fixed in 1.19.18

Votes

26

Found in [Package]

1.19.14

Issue ID

ADDR-2426

Regression

Yes

"Unable to load assets of type" errors appear if Assets have Labels when entering the Play Mode

Package: Build Pipeline - Addressables

-

How to reproduce:
1. Open project "AddressablesBug"
2. Open the "Test" Scene
3. Enter the Play Mode
4. Observe the Console window

Expected result: No errors
Actual result: Errors appear "System.Exception: Unable to load asset of type VolotRO.Gameplay.Pilots.AvatarData from location Assets/ScriptableObjects/Avatars/MaleAvatarData.asset. UnityEngine.ResourceManagement.Util.DelayedActionManager:LateUpdate () (at Library/PackageCache/com.unity.addressables@1.19.14/Runtime/ResourceManager/Util/DelayedActionManager.cs:159)"

Reproducible with: 1.19.14 (2021.2.4f1, 2021.2.7f1, 2022.1.0b2)
Not reproducible with: 1.19.14 (2021.2.3f1)
Could not test with: 2019.4.34f1, 2020.3.25f1 (Errors after downgrade)

  1. Resolution Note (fix version 1.19.18):

    Fixed issue where "Unable to load assets of type" error occurs when loading asset with classes referenced by value in "Use Asset Database" mode.

Comments (11)

  1. Quasimodem

    Mar 17, 2022 16:54

    This is a showstopper for me as well. Thus ends a painful, 2-day attempt to update Unity to 2021.2.15f1. This issue seems related to loading a ScriptableObject with a sub-asset inside it. Most certainly not fixed!

  2. Nikhil_creaxt

    Feb 22, 2022 06:51

    This issue hasn't fixed for me.
    editor : unity 2020.3.29f1
    addressable : 1.18.19

    error : System.Exception: Unable to load asset of type UnityEngine.Sprite from location

    (note : this error only happen when trying to load sprite )

  3. glenneroo

    Feb 11, 2022 22:49

    I just upgraded to the newest Unity 2021.2.11f1 which then allowed me via Package Manager to upgrade Addressables to 1.19.18 which fixes the issue.

    I should note that upgrading Unity automatically upgraded from 1.17.17 (only version I could find which didn't have this issue) to 1.19.17! I had to go into Package Manager and explicitly upgrade Addressables package.

  4. glenneroo

    Feb 09, 2022 16:25

    Since this is a showstopper and prevents my game from loading - where can we download 1.19.18 for testing? I just upgraded my project to 2021.2.10f1 and according to the docs (https://docs.unity3d.com/2021.2/Documentation/Manual/com.unity.addressables.html) 1.19.17 is the only supported version. Or can we somehow downgrade to earlier versions of 1.19?

  5. glenneroo

    Feb 09, 2022 15:46

    Also started getting this exception with any version AFTER 2020.3.22f1 LTS, including 2021.2.10f1 but only for some of my prefabs. Been pulling my hair out the last few weeks trying to figure out how I can fix this.

  6. PaulDyatlov

    Feb 07, 2022 23:55

    Any news on this? It's bothering me for a while now

  7. Verpous

    Jan 18, 2022 09:29

    I have this issue as well after upgrading from 2020.3.17 to 2020.3.26. In my testing it has nothing to do with labels. The error happens when trying to load a ScriptableObject which has a field that is an instance of a custom serializable type. So if you, say, declare some serializable struct and have a field of that type in your ScriptableObject, you will get this error.

  8. Michal_Stangel

    Jan 14, 2022 08:41

    Still not fixed with Unity 2021.2.8f1 and Addressables 1.19.17. Had to downgrade to 1.17.17.

    System.Exception: Unable to load asset of type UnityEngine.GameObject from location Assets/Core Assets/Graphics/ParticleEffects/KriptoFX/Pack4/Effect24_GroundCrack.prefab.
    UnityEngine.ResourceManagement.Util.DelayedActionManager:LateUpdate () (at Library/PackageCache/com.unity.addressables@1.19.17/Runtime/ResourceManager/Util/DelayedActionManager.cs:159)

  9. Michal_Stangel

    Jan 06, 2022 15:24

    Same error. After upgrading from Unity 2020 to 2021.2.7f1. Addressables 1.19.3 and 1.19.5.

  10. glenneroo

    Jan 05, 2022 22:45

    I also have the same error with 2020.3.25f1 after upgrading from 2020.3.22f1. If I downgrade the exceptions go away. Happens with Addressables 1.19.3 and 1.19.5. If I use Addressables 1.18.19 then I get completely different exceptions (but the exception is always in DelayedActionManager LateUpdate method (line 159).

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.