Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
Votes
0
Found in [Package]
1.1.30
2.0.1-pre.18
Issue ID
DSTR-468
Regression
No
GameObject is not removed when creating and undoing GameObject creation in a test script
Reproduction steps:
1. Open the user attached project
2. Open the Test Runner (Window > General > Test Runner)
3. Click "Run All"
4. Observe the Hierarchy
Expected result: No GameObject named "ShouldNotExistAfterTest"
Actual result: A "ShouldNotExistAfterTest" GameObject exists
Reproducible with: 1.1.30 (2019.4.36f1), 1.1.31 (2020.3.32f1, 2021.2.17f1, 2022.1.0b13, 2022.2.0a8), 2.0.1-pre.12 (2022.2.0a8), 2.0.1-pre.18 (2022.2.0a8)
Note: The created GameObject is gone after reopening the scene without saving
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
- Graphics.RenderMeshIndirect does not issue multi-draw rendering commands when using a graphics API capable of multi-draw commands
- Error "InvalidOperationException: An error occured while deserializing asset reference" is thrown when deserializing a BlackboardVariable that is a dynamically loaded monobehavior
- Removing a Camera Component from a Physics 2D Raycaster GameObject brings pop-up message twice
- UnityYAMLMerge does not open fallback merge tool when encountering merge conflicts
- Editor crash when resetting Quality settings after adding "New Group" in Mipmap Limit Groups
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.
Resolution Note (2.0.X):
Won't do any 2.0 fixes, 2.0 is never going to be released