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
- Project Auditor suggests to update package to a lower version than installed when the recommended package version is not the latest version
- Low performance when multiple meshes using BlendShape are rendered on screen
- TMP Dropdown visually corrupts or disappears when its own GameObject is assigned to "Caption Image" or "Placeholder" elements
- Usymtool tries to upload GameAssembly.pdb when it doesn't exist after building with Mono backend
- “NullReferenceException” error thrown in the Console when running HDRP Wizard “Fix All” in URP project after installing HDRP Package
Add comment