Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Votes
0
Found in
2019.3.0a10
2020.1
2020.2
2020.2.0a20
Issue ID
1268917
Regression
Yes
[Packman] Packages in Package Manager are left selected when clicking a package that has a path exceeding the maximum path limit
How to reproduce:
1. Extract the attached "1268917 repro.zip" archive directly into your drive
2. Open the "1268917 repro" project contained in the "_________________________________________117 character name__________________________________________________________" folder
3. Open the Package Manager window from Window > Package Manager
4. Select Timeline package
5. Select Cinemachine package
Expected results: Timeline package gets unselected
Actual results: Timeline package is stuck as selected
Reproducible with: 2019.3.0a10, 2019.4.7f1, 2020.1.1f1, 2020.2.0a20
Not reproducible with: 2018.4.25f1, 2019.3.0a9
Notes:
-In 2019.3 alpha versions, it's difficult to reproduce the issue because the Package Manager window is unclickable most of the time due to Cinemachine having a path that's too long. Resetting packages, restarting the Editor, and installing Cinemachine again helps to overcome this.
-Steps 4 and 5 can be repeated multiple times to get multiple packages stuck as selected
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a5
Resolution Note (fix version 2020.3):
Fixed in 2020.3.2f1