Search Issue Tracker
Fixed
Fixed in 2021.3.29f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a22
Votes
0
Found in
2020.3.47f1
2021.3.24f1
2022.2.18f1
2023.1.0b15
2023.2.0a13
Issue ID
UUM-34447
Regression
Yes
"Missing" ScriptableObjects do not throw NullReferenceExceptions when accessing their properties
How to reproduce:
1. Open the attached Project "testProject" and load Scene "SampleScene"
2. In the Project Window delete the Asset "testObj.asset"
3. Enter Play Mode
4. Observe the Console Window
Expected result: NullReferenceExpections can be seen in the Console
Actual result: No NullReferenceExceptions are thrown in the Console
Reproducible with: 2020.3.47f1, 2021.3.24f1, 2022.1.0a7, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13
Not reproducible with: 2022.1.0a6
Notes:
- Assigning a null value to a ScriptableObject correctly throws NullReferenceExceptions
- When using a GameObject instead of a ScriptableObject in this scenario, the GameObject correctly throws the Exceptions
- "Missing" GameObjects, as well as ScriptableObjects in 2022.1.0a6, get changed to "None" upon entering Play Mode
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
- [macOS] Secondary display rendering incorrect target and flickering when building for Multi-Display
- "Create Empty Child" Option Creates Root Object When No Parent Is Selected
- Freeze/Crash when entering Play Mode in a specific project
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
Resolution Note (fix version 2023.1.4f1):
Fixed in: 2023.1.4f1
Resolution Note (fix version 2022.3.5f1):
Fixed in: 2022.3.5f1