Yes, it looks like the same problem. But in our case in happens not during the build. It seems to happen when we do git pull where some graph was changed. Then I focus unity and it reimports this graph. After that some tasks rarely loose their references to UnityObjects. I can save this broken graph, then revert it in git client and references would restore.
After some debugging we found that sometimes reference.GetType() returns UnityObject instead of concrete MonoBehaviour type. And that leads to broken reference which is fixed by reverting the graph asset.
I didn’t manage to create a test project where it reproduces =( I don’t see how this issue can be related to our code, we do not influence serialization/deserialization stage.
Now I’m going to update to 3.0.8 and see if problem will be reproduced.
Login
Register
By registering on this website you agree to our Privacy Policy.