Bug Broken script references on updating custom package through package manager and committing it to git

Hello there,

In our current project we are working with custom packages hosted on github. One of the packages, which is some kind of framework for our UI, regularly causes problems.

When the corresponding package is updated on github, we of course also update it in our main project via the package manager to benefit from the changes.

The developer who updates it in the main project has no problems at all. However, if he pushes the package update (manifest.json) in the git of our main project and other developers pull this change, references to scripts of the package are lost on prefabs on their side. The game can't be started without errors anymore.

And it's not that "Missing Script" is shown on the corresponding objects but the actual script names with brackets. Sometimes it even looks like the script is correctly referenced but all fields are missing in the editor inspector. It's not event always the same script but random scripts from our custom package. If you look in the folder of the package you can see that all files are present and also updated correctly. If you click on the fields with broken references the corresponding script of the package is even selected in the project folder.

Here's a collection of broken references:







Here's what e.g. the UIManager should actually look like:



Reinstalling the package does not help. The solution is that after each pull, in which a change of the package is included, the folder of the package must be reimported manually. This is very troublesome in the workflow.



I think I setup the package correctly, putting editor scripts into and Editor folder and runtime scripts into a Runtime folder with both having their own assembly definitions. Also the package.json is setup exactly like with all other packages we are hosting on github.

So my question is: What is the reason that this problem occurs with this particular package? Can someone help me here? Maybe I am just missing something.

Cheers,
Stephan

 

Heya,
I'm getting this exact same issue - so you're not crazy!
I'm on Unity 20222.2.4f1 - and you?
Let me know if you find any solution

 

Also just discovered that all the scripts re-link when going back to the previous package commit (by reverting the package-lock.json and then refreshing the editor)

I appear to be having more success so far on 2022.2.9f1 vs 20222.2.4f1
OP - what version are you on, can you try this?

@supita
I did a debug log and I can't see anything strange in it at all.
If I get the error again on the latest editor, I'll record again and post it.
Will let you know

 

Hi there,

sorry for the delayed answer.

We were originally on 2022.2.0f1 and now moved to 2022.2.9f1. Can't tell whether the issue still persists, I will have to check with the team as it is hard to reproduce because there need to be several people/machines to be involved since the issue only happens through git. So far it looks rather good.

Thanks for your answer. I will try to file a bug report but it's hard to attach a project to reproduce as the issue mainly seems to happen through git. I will try my best to give you sufficient feedback the way you mentioned though.

I'll keep you updated.

Cheers,
Stephan

 

Hey,

glad to hear. From our experience it seems like with 2022.2.9f1 the issue doesn't persist anymore.
Thank you for the heads-up.

 

I just hit this issue on 2022.2.18 with XR Interaction Toolkit 2.4.0-pre2. Reimport fixed it as suggested by @Gentlymad - thanks!

 

Unfortunately I have to tell you that the bug still persists. By now we have 2 git packages that occasionally need to be manually reimported once someone from the team updates them through the package manager and pushes the package.json into our project's git. We are now on 2022.3.8f1. It's still not possible to create a bug report as it is hard to reproduce (happens on different machines) and I'm not sure how to turn this into a test-project since it only seems to happen through version control.

 

We are getting the same on unity 2022.3.10f

 

I am experiencing the same issue after updating XR Interaction Toolkit from v2.5.2 to v2.5.3. I occasionally have to reimport the package folder to resolve things.