Search Issue Tracker
Fixed in 1.5.1
Votes
0
Found in [Package]
1.5.0
Issue ID
1214238
Regression
Yes
[Quick Search] "ProgressOptions' does not exist in the current context" error on importing quick search package
Importing Quick Search package from Help window imports the latest package version which is not the verified version and throws "ProgressOptions' does not exist in the current context" error in the console. Going to quick search option prompts to install it again though it appears in the packages
Steps To Reproduce:
1. Create a new project
2. Help > Quick Search > Click 'Yes' when prompted to install
Expected Result: the package is installed without any issue
Observed Result: “The name ProgressOptions does not exist in the current context" error is thrown in the console
Reproducible On: 2020.1.0a21
Not Reproducible On: 2020.1.0a20, 2019.3.0f6
Environment: Win and Mac
Stack Trace: Library/PackageCache/com.unity.quicksearch@1.5.0/Editor/Providers/ADBIndex.cs(173,84): error CS0103: The name 'ProgressOptions' does not exist in the current context
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment