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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.