Search Issue Tracker
In Progress
Fix In Review for 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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment