Search Issue Tracker
Fixed
Fixed in 2.7.6
Votes
1
Found in [Package]
2.7.3
Issue ID
ADDR-4085
Regression
Yes
"Assigned editorAsset does not match type UnityEngine.Sprite" warning when assigning a Sprite to a ScriptableObject using AssetReferenceSprite
How to reproduce:
1. Create a 2D project
2. Create a ScriptableObject Script (Create > Scripting > ScriptableObject)
3. Make a public variable for an AssetReferenceSprite in the Script
4. Create the ScriptableObject (Create > ScriptableObjects)
5. Create a 2DSprite (Project > Create > 2D > Sprites)
6. Mark the 2D Sprite Addressable in the Inspector
7. Assign the 2DSprite to the ScriptableObject
8. Observe the Console
Expected result: No warning gets thrown
Actual result: Sprite does get assigned to the property field of the ScriptableObject, but a “Assigned editorAsset does not match type UnityEngine.Sprite” warning gets thrown
Reproducible in: 1.21.8 (2023.2.0a1), 2.7.3 (2023.2.0a1, 6000.0.58f1, 6000.2.5f1, 6000.3.0b2, 6000.4.0a1 (b924bdf158e1))
Not reproducible with: 1.21.2 (2023.2.0a1)
Reproducible on: Windows 11 Pro (24H2)
Not reproducible on: No other environments tested
Notes:
- Error: Assigned editorAsset does not match type UnityEngine.Sprite. EditorAsset will be null.
- The ScriptableObject does successfully load the sprite at runtime after testing, it looks like the warning is misleading.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Add comment