Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.2.6f1
2020.3
2021.1.0b8
2021.2.0a5
Issue ID
1318860
Regression
Yes
OnEnable and OnDisable are being called in wrong order
Reproduction steps:
1. Open user attached project
2. Open Assets\Scenes\SampleScene
3. Select Go 1 in the Hierarchy
4. Select Go 2 in the Hierarchy
Expected result: "OnEnable Go 1, OnDisable Go 1, OnEnable Go 2" is logged to the Console
Actual result: "OnEnable Go 1, OnEnable Go 2, OnDisable Go 1" is logged to the Console
Reproducible with: 2020.2.6f1, 2020.3.2f1, 2021.1.0b8, 2021.1.0f1, 2021.2.0a5, 2021.2.0a10
Not reproducible with: 2019.4.23f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a4
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 (fix version 2021.2):
Fixed in 2021.2.0a10