Unity 2019.3f3
Today I tried to update Addressables from 1.3.8 to 1.5.0 and it seems like it can’t load sprites anymore
Exception encountered in operation UnityEngine.ResourceManagement.ResourceManager+CompletedOperation`1[UnityEngine.Sprite], result='', status='Failed': Exception of type 'UnityEngine.AddressableAssets.InvalidKeyException' was thrown., Key=icons/engineer.png
UnityEngine.ResourceManagement.AsyncOperations.AsyncOperationBase`1:<.ctor>b__27_0(AsyncOperationHandle)
DelegateList`1:Invoke(AsyncOperationHandle) (at Library/PackageCache/com.unity.addressables@1.5.0/Runtime/ResourceManager/Util/DelegateList.cs:69)
UnityEngine.AddressableAssets.Initialization.<>c__DisplayClass13_0:<LoadContentCatalogInternal>b__0(AsyncOperationHandle`1)
DelegateList`1:Invoke(AsyncOperationHandle`1) (at Library/PackageCache/com.unity.addressables@1.5.0/Runtime/ResourceManager/Util/DelegateList.cs:69)
UnityEngine.ResourceManagement.ChainOperation`2:OnWrappedCompleted(AsyncOperationHandle`1)
DelegateList`1:Invoke(AsyncOperationHandle`1) (at Library/PackageCache/com.unity.addressables@1.5.0/Runtime/ResourceManager/Util/DelegateList.cs:69)
UnityEngine.ResourceManagement.ResourceManager:Update(Single)
MonoBehaviourCallbackHooks:Update() (at Library/PackageCache/com.unity.addressables@1.5.0/Runtime/ResourceManager/Util/MonoBehaviourCallbackHooks.cs:19)
As you can see, sprite is in group.
Every update Addressables breaks, although there is usually no breaking changes in the Changelog. I love Addressables, but updates were always nightmare.
@iamarugin InvalidKeyException… same as in my case when loading TextAsset, posted here . Nobody replied yet, prob because of the holidays. But it does work in editor, how about yours? only when i make a build (windows/exe | android/apk), it fails to load my Addressable TextAsset-s.
I made many tests, and it seems problem with the catalog/the keys (using IResourceLocators) are not there. Only in build ofc, in editor it (by default) doesnt use the built addressables content, only what you defined using addressable groups window - thats why in editor it works. When i put my addressable TextAsset into “Built In Data” group, it loads fine in build. Only fails when i put it inside custom group.
Testing TextAsset loading inside ‘Addressable Samples by Unity’ which uses Addressables v1.1.3, TextAssets load correctly on build target, which is perfect! It does confirm our suspicion, that the new version of Addressables broke something! (or did it?) I do know that the Addressables Package UI was changed recently, no more can you “Build Player Content” you now have to “New Build/Default Build Script”. Some people voiced their disagreement with that afaik, but i dont know if the build script itself was changed, thats causing these recent errors, or its some other issue. Its super simple to reproduce though. I hope someone from Unity can let us know soon! Like @unity_bill , Please!
Happy holidays!
EDIT: I now posted this in [official thread]( Addressables are here! page-9#post-5313108) also, so it gets more attention. EDIT2: I had some issues downgrading 1.5.0 ( i wanted to test older versions), so i decided to uninstall and install fresh 1.4.0, then 1.3.8 etc. What i have noticed is that my old Addressable settings stayed the same. Also the UI. Surely older Addressables versions cant be that backward compatible? So i decided to uninstall from package manager and make clean install of 1.3.8. To my surprise, after i removed, I could still open Addressables from Window/Asset Management! Surely that EditorWindow is part of Addressables plugin, which i just removed? EDIT: this menu was removed upon restart of Unity. So if you plan to downgrade, id recommend clean un/install and Editor restart. For me 1.3.8 is the last version without the bug (1.4.0 and 1.5.0 are bugged)
This needs to be submitted to the addressable team as a bug report through Unity’s bug reporting system. Expecting them to find these forum posts is unlikely. I know that the addressable team has been kind by finding issues in the forums a lot, but a bug report is the real way we can get them to fix issues. I hate that we need to spend our time making these reports. I’ve spent days of company time submitting bugs to Unity, but it’s the only way to get the dev team to realize the case that you’re encountering.
I agree with you, and also as you said ‘spending company’s time’ - rarely i have time to create a repo test project also. Considering this is a glaring bug, its gonna be found with high probability soon anyway. That coupled with the fact, that you can easily just use 1.3.8 as 1.5.0 doesn’t change the base much, i’ll just wait a bit longer. This post was also posted in the official thread, which is being frequented by unity folks more often. Anyways, after holidays, if its not reported, im gonna report it. Cheers
Having the same issue - although it doesn’t work in Editor. Works fine in build for me.
The issue was introduced in 1.4.0. We were previously on 1.3.8 and recently upgraded to 1.5.0 - but after testing, it seems that it was created in 1.4.
Any updates on this? It’s not currently a massive issue for us but would like to get resolved soon.
Yes it started @ 1.4, i mentioned this a week ago in the official thread. That’s not enough. If you want this fixed, report a bug using Unity’s Bug reporting feature. They also usually ignore reports without repo attached, so you’ll need to make one (Just heads up). As many pointed out before, don’t expect devs to scour the forum threads (like this one) for ‘mentions of bugs’, these are mostly completely missed or ignored, as forums are not a streamlined system for bug reports. There is a special case for preview-features and their threads where devs specifically ask you to mention bugs in the thread (and usually after you do that, they want you to report normally anyways).
@iamarugin it does sound like an issue with sprites we are aware of. That said, go ahead and file a bug if you don’t mind. If it ends up being a duplicate we can handle that on our end. I’d hate for this to get looked over because we fix a similar, but not exactly the same, bug.
We’ve got a ticket on our end to look into it. I’ve made it a high priority so we can hopefully get to this and figure out what’s going on soon. As per usual I can’t make any promises as to the “when” but I figure some update is better than silence.
Very frustrating bug, not sure how this slipped into a release. Makes it incredibly hard to test and one of our developers had to re-write some of our systems to get this working on editor and builds properly for testing. Please get a hot fix out for this asap.
