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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22