Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
0
Found in
2018.3.0a1
2018.3.14f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1151910
Regression
Yes
serializedProperty.objectReferenceInstanceIDValue returns 0 for missing asset references
How to reproduce:
1. Open the attached 654560.zip project
2. Go to the Assets folder-> right click in the assets window-> Create-> ScriptableObjects->and create SpawnManagerScriptableObject
3. Select "Missing" asset
4. Go to the Inspector-> Missing-> Asset and assign new created SpawnManagerScriptableObject "Data"
5. Delete from the Asset folder SpawnManagerScriptableObject "Data"
6. Go to Menu bar-> Reference-> FindReferenceID
7. Go to the Console window and inspect Debug outputs
Expected: The output for objectReferenceInstanceIDValue for missing asset reference should be the object reference instance ID
Actual: The output for objectReferenceInstanceIDValue for missing asset reference is 0
Reproducible with: 2018.3.0a1, 2018.3.14f1, 2018.4.0f1, 2019.1.2f1, 2019.2.0b1, 2019.3.0a2
Not reproducible with: 2017.4.26f1, 2018.2.21f1
Regression found in: 2018.3.0a1
Comments (2)
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
- “Create and publish WebGL builds” link leads to “Sorry about that, we can't find the page you're looking for.” page
- " Suspected crash in FXC. " shader compiler errors are thrown in a new project when creating a project in Hub with a very long name but below the maximum character threshold
- Long cloud names stretch the space in Hub when the Project dropdown is opened
- OpenGLES3 Graphics API can be used with the "Linear" Color space on unsupported GPUs resulting the error spam
- [Windows] Recommended and Downloaded Learn tabs are empty and have scrollbar
lsyu
Mar 25, 2021 12:04
Unfortunately, this is still reproducible with 2018.4.31f1