Search Issue Tracker
Fixed
Fixed in 2021.3.13f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a17
Votes
5
Found in
2021.3.8f1
2022.1.13f1
2022.2.0b5
2023.1.0a6
Issue ID
UUM-12998
Regression
Yes
“SendMessage cannot be called during Awake” warning appears when entering Play Mode if having Canvas nested in Canvas and the "Enter Play Mode Options" enabled
How to reproduce:
1. Open the user’s attached project
2. Enter Play Mode
3. Observe the Console window
Expected result: No warning
Actual result: “SendMessage cannot be called during Awake” warning appears
Reproducible with: 2021.3.6f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b5, 2023.1.0a6
Not reproducible with: 2020.3.38f1, 2021.3.5f1
Reproduced on: macOS 12.4 (Intel)
Note: Not reproducible without the “Enter Play Mode Options” setting (Edit > Project Settings > Editor > Enter Play Mode Options)
Full warning: SendMessage cannot be called during Awake, CheckConsistency, or OnValidate (Canvas: OnCanvasHierarchyChanged)
-
Tortuap
Sep 09, 2022 16:20
Can we get an update on this issue ? Its really annoying to fill the log each time I go in Play Mode.
-
Tortuap
Sep 06, 2022 21:22
It is not only that a warning message is written to log, but the main issue is that the sub canvas is not rendered at all!
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
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
- Lighting data is carried over from one Scene to another when changing Scenes in the Play Mode
- The <sprite> tag inserted image from a Sprite Asset into the UI Builder Button disappears when the Inlined Style Text Shadow Horizontal or Vertical Offset is set to be more than 0 px
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
Resolution Note (fix version 2023.1.0a17):
Fixed in: 2023.1.0a17
Resolution Note (fix version 2022.2.0b15):
Fixed in: 2022.2.0b15
Resolution Note (fix version 2022.1.23f1):
Fixed in: 2022.1.23f1
Resolution Note (fix version 2021.3.13f1):
Fixed in: 2021.3.13f1