Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.5f1
2021.1
2021.2
2022.1
Issue ID
1357510
Regression
No
Awake function called after OnEnable
How to reproduce:
1. Open the attached project "temp.zip"
2. Open the SampleScene scene
3. Press the Play button
4. Open the Console window
Expected results: Awake functions are called first
Actual results: Awake functions aren't called first
Reproducible with: 2019.4.29f1, 2020.3.17f1, 2021.1.16f1, 2021.2.0b7, 2022.1.0a5
Notes:
- Changing scripts order in the inspector doesn't change results
- When both functions (awake and onenable) are in different scripts this bug happens
- If both functions are in the same script everything works fine
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
- Console Warning -- KeyboardIconAtlas sprite Input Outline goes beyond the boundary of the Sprite rect.
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
Resolution Note (2022.1.X):
Enable and Awake messages are handled "by component", not "by game object". We guarantee that for a given component, the Awake message is received before the "Enable" message. But we don't guarantee this across component: the reported screenshot is valid in that sense: by design, EnableLog behaviour can receive both its Awake and Enable events before the AwakeLog behaviour receives any of the messages.