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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.