Search Issue Tracker
Fixed
Won't Fix in 6000.3.X, 6000.4.X
Fixed in 6000.5.0a7
Votes
0
Found in
6000.3.0b1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-119249
Regression
No
Hierarchy v2: [Correctness] Replace prefab in context mode and undo doesn't remove nodes properly
Steps to reproduce:
- Open a prefab in context mode using >
- Select a child object of the prefab and right click -> select prefab -> replace with a different prefab
- Undo
Actual results: The prefab used for replacement doesn't get removed properly
Expected results: The new prefab should be removed and the previous child node displays
Reproducible with versions: latest main
Tested on (OS): mac
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7
Resolution Note (6000.4.X):
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.
Resolution Note (6000.3.X):
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.