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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a22