Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.2.0f3
2017.3.0f3
Issue ID
993592
Regression
Yes
Applying a prefab throws NullReferenceException
To reproduce:
1. Open the project, attached by the user (Assets.zip)
2. Open the "Menu" scene
3. Select Standard Scene Manager game object in the Hierarchy
4. In the Inspector, press Apply
5. Observe the console
Reproduced in 2017.2.0f3, 2017.2.1p3, 2017.3.0f3, 2018.1.0b5
Did not reproduce in 2017.1.3p1, 2017.2.0f2
Regression introduced in 2017.2.0f3
Comments (6)
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
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
LT23Live
Jun 05, 2018 22:39
I am running into this issue too. Alongside that, sometimes when we bring the prefab back in, the assets aren't in the applied position. This has only been tested with UI elements for the canvas.
ForteBass
Feb 16, 2018 23:42
I encountered this too. Worked around it by dragging the affected hierarchy member onto the existing prefab of that object.