Search Issue Tracker
Fixed
Fixed in 6000.0.25f1, 6000.1.0a2, 7000.0.0a4
Won't Fix in 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.37f1
2022.3.23f1
6000.0.0b14
7000.0.0a1
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
We do not have bandwidth to fix this kind of bug.
Resolution Note (fix version 7000.0.0a4):
Search: Fixed Scene Provider search when a string property is a numerical value.
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.25f1):
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.