Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-35196
Regression
No
“OnDisable” function is executed based on script order in the Inspector window but not Script Execution Order
How to reproduce:
1. Open the user’s attached “TestOrder.zip” project
2. Enter Play Mode and exit Play Mode
3. Observe the Console window
Expected result: “First OnDisable”, “Second OnDisable”, and “Third OnDisable” are logged
Actual result: “Third OnDisable”, “First OnDisable”, and “Second OnDisable” are logged
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Reproduced on: macOS 13.2.1 (Intel)
Note: Not reproducible with the “OnEnable” function
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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
Resolution Note:
Changing the execution order of OnDisable() to respect ScriptExecutionOrder would be a breaking change.
Resolution Note (2023.2.X):
Changing the execution order of OnDisable() to respect ScriptExecutionOrder would be a breaking change.