Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.2
2021.2.0b1
2022.1
Issue ID
1345194
Regression
No
Missing default references show up as none in ScriptableObject Script asset
Reproduction steps:
1. Open the attached project (1345194.zip)
2. Notice that both the Script (ScriptWithMissingReference) and the ScriptableObject (Bug Example) assets reference New Material
3. Delete the New Material asset
4. Notice that the reference in Script says 'None (Object)' whereas in ScriptableObject it says 'Missing (Object)'
5. Restore New Material
6. Notice that both the ScriptableObject and the Script reference New Material again
Expected result: Both the ScriptableObject and the Script say 'Missing (Object)' as both remember it
Actual result: The Script says 'None (Object)'
Reproducible with: 2018.4.33f1, 2019.4.28f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b2, 2022.1.0a1
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a12