Addressable Group References Becoming Unhooked, Schema Assets Deleted When Switching Changesets?

Unity Engine
1

Hello!

I’ve been attempting to make use of the Addressables system, but one problem my team keeps running into is that often upon swapping between changesets using PlasticSCM, the ‘Addressables Groups’ window will suddenly become empty (where it is supposed to contain a number of Addressable groups!)

The group assets THEMSELVES continue to exist, but for some reason the editor is choosing to a) remove all references to them in AddressableAssetsSettings.asset, b) remove all references to the auto-generated schema assets within e.g. “Packed Assets.asset”, and c) actually delete the existing schema assets that had been sitting in the project (the ones in the Schemas folder that have long GUIDs in their asset names).

These various undesired project modifications end up showing in version control as modifications and and deletions; thus if I revert these, things return to normal and my project stuff is all still functional & intact! Yet of course it’s not reasonable to ask everyone on the team to ‘save project and then revert’ every time they hop changesets, haha.

I’ve been attempting to narrow down some specific trigger for this phenomenon, but unfortunately it’s pretty elusive! Sometimes swapping between two particular changesets will reliably repro the issue, but other times it will not. And even if I did find a 100% repro case, it isn’t so convenient to somehow include a version control repo in my bug report, haha. (Bug reporting is a pretty arduous task at the best of times when it comes to projects that are in production!) One thing I seem to know for certain at this stage is that it only really happens while unity is doing library updates, reimporting assets etc.

Has anybody seen something like this before? Did I miss a forum post or UnityAnswer that might help? Am I overlooking some obvious thing? It’s becoming kind of a dire situation for us, haha.

3 Likes
2

I have exactly the same problem addressables is deleting my groupschemas and assetgroups , but it seems they just ignore my post. it is very hard to reproduce and i searched editor.log and find nothing

1 Like
3

Same problem here.
@davidla_unity @unity_bill : We desperately need some educated guesses here, can you help?

4

yeah, it will be a total disaster if you are not using a version control.

5

Hey all, apologies for the late response. I, unfortunately, haven’t seen this yet personally so it’s hard to hazard any guesses at the moment. We’ll start looking into it. In the meantime has anyone submitted a bug with Unity? I understand it’s not reproducing 100% of the time but anything helps.

6

Just to get a little more information, when this is happening are you seeing anything in the log? Any errors or warnings? What version of the editor and what version of the package are you using?

7

I’ve encountered it across a few versions, but at the moment we’re on 2019.3.0b8, and Addressables is rolled up to 1.3.8.

I have been whittling away at the project on a quarantined branch with a view towards filing a bug report! I’ve established a 100% repro case involving a switch back and forth from two changesets (actually I’ve iterated through a wide variety of changeset pairs where this happens over the past couple days, but still trying to work out what specifically it might be about them). Below you can find the editor log output beginning from the moment after I maximize the editor after a branch change, triggering this error to occur! I don’t notice anything amiss about it, personally…

8

@bvance I appreciate your effort in tracking this down. Glancing over that editor log a couple times nothing really pops out at me either. What version control are you using? I’ve been trying to reproduce this and the only time something remotely similar occurred was when I caused a merge conflict on the “Packed Assets.asset”. But there were multiple errors logged when that happened. No one that’s running into this appears to have reported any logged errors so I’m guessing you’re not seeing anything like that?

9

I’ve been noticing this error get spammed into upm.log, though I’m not very sure it’s related:

10

Hmm… probably isn’t but thanks for the information. I’ll see what I can figure out. Thanks!

11

I have submitted a bug report! Case 1199672

We are using PlasticSCM for version control, but I found that I was able to reproduce the issue simply by importing some assets out of a unitypackage I created (this is what I did for the bug report). Basically it does not appear to me that PlasticSCM needs to be involved in any way for this bug to manifest!

It SEEMS important that the imported assets overwrite existing assets in order for this to happen; every time I tried adding or removing various assets, the Addressables remained intact. The simplified project in my bug report has been stripped of literally every irrelevant asset and package, so it doesn’t seem like any kind of compatibility problem with other code! We’ve been able to reproduce this issue using my example project (the one I included in the bug report) on a couple of different systems, so I’m not sure whether it’s a workstation configuration thing either. Frankly it’s very mysterious!

I really feel like I must be making some obvious mistake that I’ve just become blind to from staring at this too long, lol. Hope this bug report is helpful!

2 Likes
12

Thank you, I really appreciate that.

13

Are there any updates on this?

14

@taylank1 we have a fix in the works. There’s only been one method that has let us reproduce this consistently locally so we’re trying to make sure the fix will hopefully work for as many use cases as possible.

I believe we’re also going to remove the automatic cleanup of null groups on asset import. This should hopefully keep us from removing some things before we need to.

If all goes well, this should be in the next release or the one just after at the latest.

2 Likes
15

That’s great news. Thanks, David!

16

This is good news!

When we talk about ‘releases’, are we talking about e.g. 2019.3.x, or about an update to the Addressables package, or BOTH? Haha, it’s exciting times with this newer dependency management tech working!

17

@bvance typically for us (on the Addressables forum) if we’re talking about releases we mean package releases, not editor ones. Hope that helps!

2 Likes
18

Glad to see we’re not the only ones with this issue, and hoping a fix soon. It’s already hard enough to navigate the new API without randoms breakdowns of the system on its own ^^;

Thanks @bvance for your work on cracking this bug!

1 Like
19

Issue tracker link! Unity Issue Tracker - [Addressables] Group References get unhooked and Schema Assets get deleted when re-importing certain assets

1 Like
20

If you’re still experiencing this issue can you try updating to 1.5.1. We should hopefully have this fixed in that release. Thanks!