Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2019.3.0f5
2020.1
Issue ID
1213245
Regression
No
.unitypackage files are not recognized by the Editor's Project window when Unity versions are uninstalled using Hub
How to reproduce:
1. Open the 'project-1213246.zip' project using the EnvIronman VM
2. In the Project window observe the 'test.unitypackage' asset
Expected result: .unitypackage file has Unity Editor icon and can be double-clicked to import Assets
Actual result: .unitypackage file has no icon and cannot be double-clicked to import Assets
Reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a20
Note: double-clicking .unitypackage fixed in 2019.3.0f6 and 2020.1.0a19
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
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22