Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.22f1
2023.2.15f1
6000.0.0b11
Issue ID
UUM-67337
Regression
No
NullReferenceException is thrown when changing the missing Script in the Prefab mode
How to reproduce:
1. Open the user-attached project “Test”
2. Open the “Flying Missile Launcher” Asset in the Prefab mode
3. Find the “(Script)” missing Script Component in the Inspector
4. Assign any Script to it
Expected results: The Script is assigned and no errors are thrown
Actual results: The Script is not assigned and the NullReferenceException is thrown
Reproducible with: 2022.3.22f1, 2023.2.15f1, 6000.0.0b11
Can’t test with: 2021.3.36f1 (Compilation errors)
Reproducible on: Windows 11 Pro, Windows 10 (user-reported)
Not reproducible on: No other environment tested
Note: Some Scripts get assigned but they still throw an error
First lines of the error:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.UIElements.Bindings.SerializedObjectBindingToBaseField{{2[TValue,TField].FieldValueChanged (UnityEngine.UIElements.ChangeEvent}}1[T] evt) (at <d364f36063f14416baef5d128b2fc608>:0)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.