Search Issue Tracker
By Design
Votes
0
Found in
2020.1
2020.1.0a1
2020.1.9f1
2020.2
2021.1
Issue ID
1300568
Regression
Yes
Package Manager does not match all string patterns when searching in "My Assets"
How to reproduce:
1. Create a new Unity project
2. Open Package Manager
3. Select "My Assets"
4. Type in a substring of the asset that doesn't contain the first letter
Expected results: A string pattern matching algorithm is used that matches all patterns
Actual results: A string pattern matching algorithm is used that matches only from the start of the string
Reproducible with: 2020.1.0a1, 2020.1.17f1, 2020.2.1f1, 2021.1.0b1
Not reproducible with: 2019.4.17f1
Could not test with: 2018.4.30f1 (No "My Assets" section)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2021.2.X):
Not a bug according to the Genesis team.
The `minotaur` package not matching the `taur` search string is not just in the Package Manager UI side, but also on the asset store backend.
It is the expected behaviour of the search API from the asset store back end. Only exact match and prefix match can get the results (with 1-distance typo tolerance).