Search Issue Tracker
Fixed in 6000.0.25f1
Fixed in 6000.0.X, 6000.1.0a2, 7000.0.0a4, future release
Won't Fix in 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.37f1
2022.3.23f1
6000.0.0b14
Issue ID
UUM-69142
Regression
No
Search results are not displayed when a string property is a numeric value
Reproduction steps:
1. Open the attached “UnitySearchBugTest.zip” project
2. Open the “SampleScene” (Scenes > SampleScene)
3. Press Ctrl + K
4. Enter "t:BugTest #str:12" in the Unity Search window
5. Observe the search results
Expected result: “BugTest2” comes up in the search result
Actual result: No search result comes up
Reproducible with: 2021.3.37f1, 2022.3.23f1, 2023.2.17f1, 6000.0.0b14
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note:
- Search works as intended when the “Str” property is a text value
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 6000.0.25f1):
We do not have bandwidth to fix this kind of bug.
Resolution Note (fix version future release):
Search: Fixed Scene Provider search when a string property is a numerical value.
Resolution Note (fix version 7000.0.0a4):
We do not have bandwidth to fix this kind of bug.
Resolution Note (fix version 6000.1.0a2):
Search: Fixed Scene Provider search when a string property is a numerical value.
Resolution Note (fix version 6000.0):
Search: Fixed Scene Provider search when a string property is a numerical value.
Resolution Note (2022.3.X):
Fix is too risky for 22.3.
Resolution Note (2021.3.X):
Fix is too risky for 21.3.