Search Issue Tracker
Fixed
Fixed in 2023.1.X, 2023.1.0a16
Votes
1
Found in
2020.3.37f1
2021.3.7f1
2022.1.11f1
2022.2.0b3
2023.1.0a4
Issue ID
UUM-10221
Regression
No
[Quick Search] Object Selector doesn't suggest Script Components that contain a namespace in the naming
How to reproduce:
1. Open the attached “case IN-7005” project
2. Open the “Test” Scene
3. Select the “User” GameObject in the Hierarchy
4. Open the Object Selector for the “Target 2” field in the Inspector
Expected result: “Target 2” GameObject is suggested to select
Actual result: No suggestions are presented
Reproducible with: 2020.3.37f1, 2021.3.7f1, 2022.1.11f1, 2022.2.0b3, 2023.1.0a4
Workaround:
Remove the namespace specifier in the search query (i.e., change "t:searchtest.searchtarget2" to "t:searchtarget2")
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