Search Issue Tracker
Fixed
Fixed in 2022.3.57f1
Votes
0
Found in
2022.3.55f1
Issue ID
UUM-91728
Regression
No
Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
How to reproduce:
1. Open the “IN-91536-UiToolkitQueryNull.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Console
Expected result: The last error starts with “ArgumentNullException: Value cannot be null.“
Actual result: The last error starts with “NullReferenceException: Object reference not set to an instance of an object“
Reproducible in: 2021.3.47f1, 2022.3.55f1, 6000.0.15f1
Not reproducible in: 6000.0.33f1, 6000.1.0a10
Fixed in: 6000.0.16f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
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
Add comment