Search Issue Tracker
Fixed in 2.8.1
Votes
0
Found in
1.28.0
2.7.4
Issue ID
UUM-131137
Regression
Yes
"Assigned editorAsset does not match type TObject" warning when assigning a class inheriting from TObject to a ScriptableObject using AssetReferenceT<TObject>
Reproduction steps:
1. Open the attached project "WarningAssetReference.zip"
2. Select the "Assets/Example.asset" in the Project tab
3. Assign "Assets/Inheritance.asset" to "AssetReference" in the Inspector
4. Observe the Console
Expected result: No warning gets thrown
Actual result: "Assets/Inheritance.asset" does get assigned to AssetReference, but a "Assigned editorAsset does not match type Base. EditorAsset will be null." warning gets thrown
Reproducible in: 1.21.3 (2023.2.0a1), 1.28.0 (2023.2.0a1), 2.7.4 (6000.0.60f1, 6000.2.8f1, 6000.3.0b5, 6000.4.0a3)
Not reproducible in: 1.21.2 (2023.2.0a1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2.8.1):
Fixed an issue where applying an asset of an inherited type to an AssetReferenceT of the base type no longer throws warnings incorrectly
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug for this version. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case for the 1.X release stream, but will be continuing with a fix for the 2.X stream. Thank you again for taking the time to report this issue.
Resolution Note:
Fixed an issue where applying an asset of an inherited type to an AssetReferenceT of the base type no longer throws warnings incorrectly