Addressables 1.1.9 keeps losing assets!

So updated to 1.1.9 today, and randomly Addressables keep going missing.
Can't pinpoint why this is happening. But whenever it does, I need to close and re-open Unity.
When it does happen, I can't clean or build player content. Nothing happens.



Enter play mode:

Code (CSharp):

1. Exception encountered in operation UnityEngine.ResourceManagement.ResourceManager+CompletedOperation`1[UnityEngine.GameObject], result='', status='Failed': Exception of type 'UnityEngine.AddressableAssets.InvalidKeyException' was thrown., Key=b2a8a8a8a65113b4585433020eac0723
2. UnityEngine.AddressableAssets.AssetReference:InstantiateAsync(Transform, Boolean)

 

I second this critical bug - relaunch unity editor will mark all paths as *missing file*. So the [build player content] will do nothing.

unity 2019.1.8f1
addressables 1.1.9

@unity_bill

 

Refs https://forum.unity.com/threads/add...in-cloud-build-after-upgrade-to-1-1-9.733208/

Could be the same bug.

 

This is happening to me to, starting with 1.1.9. Reverted to 1.1.7, and it's no longer happening.

In my case, if I restart the editor, it seems to work for a bit. But after entering play mode once or twice, every asset will have a path of "Missing File", despite the actual assets being where they've always been. I'm not sure what other information I can provide. For now, I'm back to 1.1.7.

 

Same. I also experience this.
Unity 2018.4.6f1
Addressables 1.1.9

Reverting to Addressables 1.1.7 restored the files with no apparent issue.

Am not using cloud build. All builds are local.

 

Omg.
Same errors. (1.1.9) 2019.2.2f


I am starting to lose faith in the addressables......

 

I did not even have "missing reference" words in addressables window, only absence of icons. It happened for only one whole group but not for every group.

 

Yeah, 1.1.9 fixed a dependency issue for me but introduced like 5 more

 

Seems to happen mostly when adding new addressables into the system.
The old addressables become missing. I'll try and get a repo bug report soon

 

So, when you first launch Unity, the paths are there, then you take some action, and they go away? Or when you launch Unity they are gone?

This is definitely something we want to work out asap.

 

Yes, when I launch Unity they are there.
It seems whenever new addressable prefabs or changes to existing addressable prefabs are made, the system is unable to find any other addressable assets. The only way to recover from this is to close and re-open Unity.

It's already happened 3 times for me today, will try and submit a bug report later.

 

Same here, but in my case not was at the same time when I updated addressables to 1.1.9, I was working like two days without problem with 1.1.9, and today all the paths are lost.

 

Same issue with Unity 2018.4.5f1

 

Still trying to reproduce this. Seems that it doesn't happen when the addressables window is open.

 

Well, we have been unable to repro this, but looking at the code diff, I'm 83% sure I've found the issue. Since we can't actually verify the fix, I'm hoping someone on this thread can. I've attached a zip that is identical to version 1.1.9 except for a small change that hopefully fixes this.

Those that have run into this, please unzip this in your Packages directory and see if the issue goes away.

 

Wish I saw this post earlier before deleting and rebuilding all my addressables and then having issue just pop back up again.

Anyway, after downloading the updated version you just posted it appears to have solved my issue. Going to be doing a few more hours work on this project today so will try to confirm.

 

@unity_bill it works for me, after applying another community patch for the await task bug. Thanks for the fix.

 

This bug has hosed off my entire setup multiple times now.

• Once after attaching VS debugger and then hitting play.
• Once when I was playing around with installing and removing various packages.
  
  
• And just now the first run after rebooting from a computer blue screen. I added a new addressable, added a new group, dragged an asset into the group (all the Path references still showed up in the UI at this point). After hitting PLAY it seemed to compile a bunch of shaders or something with a progress bar (running in Virtual mode). Once it started playing, all the references in the UI now showed "Missing File".

 

On my side switching from 1.1.7 to 1.1.9 lose all the references to the groups and assets.
Event the default Built In Data group.

Edit : I was able to recover the Built In Data group by changing EditorGUI.DisabledScope(true) to false on the line 139 of the following file AddressableAssetSettingsInspector. And add the group to the list again.

 

Thanks for testing it. We'll get a patch fix out soon.

 

Yes the patch seems to be working for me as well.
Just curious what the issue was?

 

Basically our code was this:

Code (CSharp):

1. string cachedPath;
2. public AssetPath
3. {
4. get
5. {
6.   if(cachedPath == null)
7.   { cachedPath = SomeLogicBasedOnGUID... }
8. }
9. }

The issue is that there is apparently some temporary state you can somehow get in where the GUID is invalid for a very short amount of time. While it was invalid, it was setting the cachedPath to "". So our check for null was always false, and it was stuck as "" forever. Changing

cachedPath == null

to

string.IsNullOrEmpty(cachedPath)

was the meat of the fix (there's some other small cleanup in there, but that fix is the main part).

 

Ah nice. Well, thanks for for the prompt fix, looking forward to next update

 

Addressables 1.1.10 released a short while ago. It fixed the issue I was having with Cloud Build.