Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a2
Issue ID
1051601
Regression
No
Assertion failure when discarding changes after nesting a Prefab in Prefab Mode
If you are editing a Prefab in Prefab Mode, add another Prefab to the hierarchy and then back out and discard changes, an assertion failure will take place.
Assertion failed on expression: 'prefabInstanceFileID != 0'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
Assertion failed on expression: 'fidA != 0'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
1. Install Unity
2. Open the attached project
3. Find PrefabA in Assets and open in Prefab Mode
4. Make sure Autosave is OFF
5. Add PrefabB to PrefabA
6. Exit Prefab Mode and discard changes
Result:
Assertion Failures occur.
Expected Result:
No errors should appear in the Console.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment