Search Issue Tracker
Fixed in 2019.1.X
Votes
2
Found in
2017.4.0f1
2018.3.6f1
Issue ID
1128790
Regression
No
Unity throws "SendMessage cannot be called during Awake, CheckConsistency, or OnValidate" Warning when manipulating the UI
To reproduce:
1. Download attached project “SendMessageSpam.zip" and open in Unity
2. Open "SampleScene" scene
3. In Hierarchy select UI > Canvas > Parent > Slider
4. In Inspector modify Slider Value
Expected results: No Warning or Error are printed in Console
Actual results: Console spams "SendMessage cannot be called during Awake, CheckConsistency, or OnValidate" Warnings with each modification
Notes:
- This issue appears on Windows, macOS and Linux
- Link to the project is attached in Comments section
- A Video which shows how to reproduce the issue is attached in Comments section
Reproduced on Unity 2019.3.0a12, 2017.4.0f1, 2017.4.20f2, 2018.3.7f1, 2019.1.0a4
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
bourriquet
Jun 20, 2020 23:06
A buyer of my code asset has this problem too with Unity 2019.3.13, but I cannot reproduce it. It might have to do with some other settings. It comes from a LoadAssetAtPath call in a OnGUI function in a Custom Drawer script.
stjernerlever
Mar 04, 2020 09:42
Just updated my project from 2018.3 to 2019.3 and started receiving this error. Points to an OnValidate function, although it seems to be carrying out its function as intended.
FIFTYTWO
Feb 19, 2020 05:06
Unity 2019.3.1f1 the message here again. They are appearing mainly while project just opening. Some of them had call stack that lead to custom ScriptableObject or Prefab assets where our scripts accessed some singleton editor setting assets via AssetDatabase.LoadAssetAtPath(). So, I reworked these OnValidate to delay the validation during cold start. But there are still a lot of such messages with no call stack behind. So, I have no idea are they related to my assets or system ones.
Gladyon
Feb 04, 2020 12:53
Could you please really fix the problem please?
I am using Unity 2019.2.17f1 and it's still there.