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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22