Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2022.2.14f1
2023.1.0b11
2023.2.0a10
2023.3.0a3
Issue ID
UUM-32752
Regression
Yes
“SendMessage cannot be called...” warnings are thrown in the Console when undoing and redoing new GameObject creation under Parent Canvas GameObject
Reproduction steps:
1. Open the attached “2022_2_Test.zip“ project
2. Open the “SampleScene” scene
3. Create Empty GameObject under “BadCanvas” GameObject
4. Undo and redo the last change
5. Observe the Console
Expected result: Console throws no warnings
Actual result: “SendMessage cannot be called during Awake, CheckConsistency, or OnValidate (InputField: OnRectTransformDimensionsChange)” warnings are thrown in the Console
Reproducible with: 2022.1.0b1, 2022.2.0a1, 2022.2.14f1, 2023.1.0b11, 2023.2.0a10
Not reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.1.0a16
Reproduced on: Windows 10
Not reproduced on: macOS Monterey 12.6 (Intel)
Notes:
-Warnings are thrown only on “BadCanvas” GameObject
-Issue is not reproducible on “BadCanvas” GameObject duplicate
-Issue is not reproducible if “Parent” GameObject Image has no Sprite assigned or if the Horizontal Layout Group Component of “BadCanvas” GameObject is disabled
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.
Resolution Note (2023.3.X):
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.