Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.2.0f2
Issue ID
956238
Regression
No
Prefab instance is shown as disconnected in Hierarchy if it contains a component with a missing script
How to reproduce:
1. Open users attached project
2. Inspect "Prefab", note that it has a "NewBehaviourScript" attached
3. Delete the 'NewBehaviourScript' script asset (from Project folder)
4. Drag 'Prefab' into Hierarchy/Scene
Expected result: "Prefab" text is still shown in a blue color, indicating that it is connected to a main "Prefab"
Actual result: "Prefab" text is shown in white, as it would be disconnected from a main "Prefab", clicking Apply or Revert throws a Null Reference Exception
Reproducible with - 2017.3.0a4, 2017.2.0f3, 2017.1.2f1, 5.6.3p4
Notes:
1. Clicking "Revert" or "Apply" on the "Prefab" instance causes a Null Reference Exception being thrown (the "Apply" one was not reproducible up until 2017.3.0b1 and 2017.2.0f3)
2. Even though the "Prefab" instance is shown as disconnected, new components and changes are still applied to a main (originating) Prefab
Fixed in - 2018.3.0b5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment