Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.5f1
2023.1.5f1
2023.2.0a23
2023.3.0a1
6000.0.0b11
Issue ID
UUM-42934
Regression
Yes
[Undo] “Missing Prefab with guid“ GameObject appears after deleting a nested prefab if using undo to remove its parent from the Hierarchy
How to reproduce (simplified, see History below for original description):
1. Create a nested Prefab with a "Nestor" and a "Nestee"
2. Instantiate "Nestor" by dragging it from the Project window into the Hierarchy
3. Delete “Nestee” from the Project window
4. Press undo until the instance "Nestor" will be removed from the Hierarchy window
5. Observe the Hierarchy and Console window
Expected result: “Nestor” GameObject is removed and no errors appear
Actual result: “Missing Prefab with guid“ GameObject appears and multiple errors and a warning appears
Reproducible with: 2022.1.0a12, 2022.1.24f1, 2022.3.5f1, 2023.1.5f1, 2023.2.0a23
Not reproducible with: 2021.3.28f1, 2022.1.0a11
Reproduced on: macOS 13.4.1 (Intel)
Note: with some Editor versions when selecting “Missing Prefab with guid“ GameObject then the “ArgumentNullException: Value cannot be null” error appears in the Console window
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
- Warnings in the Bug Reporter window are cut off and not truncated when the Bug Reporter window is resized to its minimum size
- Color is incorrectly applied to objects when initialized with non-normalized parameters
- SerializationUtility.GetManagedReferencesWithMissingTypes() don't return null when “Prefab has missing SerializeReference Types“ warning banner is present
- Memory leak when VFX Graph is open and Camera has "Target Texture" enabled
- The Canvas component's warning box is missing an apostrophe when Additional Shader Channels is set to "Normal" and "Tangent" with Render Mode set to "Screen Space - Overlay"
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.