Our sample project that works perfectly fine on all Unity versions from Unity 2017.4.32f1 to Unity 2019.4.21f is completely broken when opened with Unity 2019.4.23f1.
We get NullReferenceExceptions, ArgumentNullExceptions, etc.
We can run a scene and make a build, but the game is completely broken.
Bug reported: 1327540
*You can pull the same working project from a bug report that was reported on Unity 2019.4.18f1
Expect to see this error a LOT. It’s easily the most common thing to do when working. Learn how to fix it rapidly. It’s easy. See the above link for more tips.
This is the kind of mindset and thinking process you need to bring to this problem:
Step by step, break it down, find the problem.
When you have identified more where the problem is, here is how to get help in the forums:
How to report your problem productively in the Unity3D forums:
Thank you for this detailed info. We have backups and we also use git. This is a sample project which we use to test the new Unity versions and report bugs.
Some references in our prefabs in the inspector are missing, like wheel colliders, wheel models, audio sources, and other stuff that were assigned and worked without any issue in Unity 2019.4.21. Prefabs are all messed up, we have many prefabs, many scenes, this is a nightmare.
We tried to rebuild our scene but there are many “hidden” issues, like ArgumentNullException: Value cannot be null. Parameter name: Source. The object that is pointed by this error is completely the same as in Unity 2019.4.21 with all references, and when we double-click this error we get:
The path /Users/bokken/buildslave/unity/build/Modules/Audio/Public/ScriptBindings/Audio.bindings.cs’ does not seem to exist anymore on disk.