Search Issue Tracker
Won't Fix
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
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
Resolution Note:
Changing the execution order of OnDisable() to respect ScriptExecutionOrder would be a breaking change.