Search Issue Tracker
Fixed in 2022.2.3f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a23
Votes
0
Found in
2021.3.11f1
2022.2.0b10
2023.1.0a13
Issue ID
UUM-17774
Regression
No
The Search window returns wrong types of assets when using t:prefab query
Reproduction steps:
- Open the “LocTable” project
- Press CTRL + K
- In the Search window type “t:prefab”
Expected result: One prefab appeared in the search results
Actual result: One prefab and .fbx asset appeared in the search results
Reproducible with: 2021.3.11f1, 2022.1.19f1, 2022.2.0b10, 2023.1.0a13
Could not test with: 2020.3.40f1 (The Search window is not introduced)
Reproduced on: Windows 10
Note: issue also reproduces in the Project window with enabled Advanced search 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
- 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 2022.2):
fixed in 2022.2.3f1