Search Issue Tracker
Fixed in 1.6.0-preview.4
Votes
0
Found in [Package]
preview.3 - 1.5.0
Issue ID
1225947
Regression
No
Quick Search fails to find assets when more than 16 characters are entered into the search field
How to reproduce:
1. Open the attached 'project-1225947.zip' project
2. Open Quick Search (ALT + ')
3. Type 'VerySuperLongAssetName'
Expected result: the asset is found in the search results
Actual result: the asset is NOT found in the search results
Reproducible with: 2018.4.19f1, 2019.3.4f1, 2020.1.0b1, 2020.2.0a2 (preview.3 - 1.5.0, 1.5.1, 1.6.0)
Not reproducible with: 2018.4.19f1, 2019.3.4f1, 2020.1.0b1, 2020.2.0a2 (preview.3 - 1.4.2, preview.2 - 1.5.0)
Could not test with: 2017.4.38f1 (Package Manager not available)
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 1.6.0-preview.4):
Fixed in the preview.4 - 1.6.0 Quick Search package version.