Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
2
Found in
2020.3.35f1
2021.3.3f1
2022.2.0a16
Issue ID
UUM-2494
Regression
No
SendMessage cannot be called' warning is thrown when calling AssetDatabase.LoadAssetAtPath
Reproduction steps:
1. Open the attached 'PlayableDirectorSendMessage' project
2. In the Project window select the 'Assets/Prefab.prefab'
3. Observe the Console
Expected result: No warnings are in the Console
Actual result: Several 'SendMessage cannot be called during Awake, CheckConsistency, or OnValidate (sprite: OnSpriteTilingPropertyChange)' warnings are in the Console
Reproducible with: 2019.4.39f1, 2020.3.34f1, 2021.3.3f1, 2022.1.2f1, 2022.2.0a15
Reproduced on: macOS 11.6 (Intel)
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
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
- Physics Debugger displays mouse cursor ray casts when Game view is not open if Input System package is used
- “ArgumentException” error thrown when disabling all columns in Project Auditor's Multi-column panel context menu
- Errors are thrown and contextual menu does not open when right-clicking multiple mixed keyframes in Dopesheet
- Crash on MergeObjectCollection when repeatedly selecting a Prefab Asset in the Project Browser
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (2022.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.