Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.2.0b4

6000.3.0a4

6000.4.0a1

6000.5.0a1

Issue ID

UUM-108789

Regression

No

Error "Cannot destroy Component while GameObject is being activated or deactivated." logged when undoing deletion of Game Objects under Prefabs

Scene Management

-

Steps to reproduce:

  1. Create a URP Project and import the attached Asset Package
  2. Open Prefab "PackagedPlayer"
  3. Select "GameObject" in the Hierarchy and enter Play Mode
  4. In the Component "UI Document" click the button "Create Panel Input Configuration"
  5. Delete it in the Hierarchy and undo this action
  6. Exit Play Mode, Delete it again and undo this action

Actual results: Error "Cannot destroy Component while GameObject is being activated or deactivated.
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()" is logged

Expected results: No errors are logged

Reproducible with versions: 6000.2.0b4, 6000.3.0a4

Not reproducible with versions: 2022.3.63f1, 6000.0.50f1, 6000.1.6f1 (No World Space UI flag in Panel Settings)

Tested on (OS): Windows 11

  1. 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.

  2. Resolution Note (6000.5.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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.