Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
1
Found in
5.6.0b5
Issue ID
1056446
Regression
No
Undo after Unpacking/deleting prefab Completely on an instance with missing asset does not properly return to previous state
To reproduce.
1. Create prefab.
2. Delete its asset.
3. Unpack prefab instance of this prefab.
4. Press undo.
Expected result: After undo, prefab is shown as red missing prefab instance.
Actual result: Nothing changes after undo.
Seems that the PrefabInstance object is not properly reconstructed when looking at the debug mode in the Inspector
Reproduced on: 2019.1.0a11, 2018.3.0b12, 2018.3.0a6
Scenario 2
1. Create any gameobject and make a prefab of it.
2. Delete the prefab from the project window.
3. Delete the prefab instance from hierarchy. (It appears red because of the deleted asset)
4. Undo. (Gameobject appears in the hierarchy)
5. Make a prefab of the restored gameobject by dragging it to project folder.
Expected Result: Errors appear in the console.
Stack Trace:
1. AssetImporter is referencing an asset from the previous import. This should not happen.UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
2. Assertion failed on expression: '!GetPersistentManager().IsStreamLoaded(metaDataPath)'UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
3. Asset import did not unload metadata path. This will leak memory. File a bug with repro steps please. (Assets/Cube.prefab)UnityEditorInternal.InternalEditorUtility:ProjectWindowDrag(HierarchyProperty, Boolean)UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash after the “State comes from an incompatible keyword space“ log when opening the project
- [Android] GameObject are not rendered at all or rendered black when in the custom shader “multi_compile_instancing“ is enabled with two “float4” instance properties are present on older devices
- LineRenderer.BakeMesh generates a box-shaped MeshCollider when the camera's Y-axis rotation is in a specific range
- Different build sizes between Editor build and command-line build when "Static Batching" is enabled
- Particle System "Start Rotation" property affects a different axis when upgrading to newer Editor versions
Add comment