Search Issue Tracker
Fixed in 2021.1.X
Votes
1
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1266321
Regression
No
[macOS] "Failed to import package with error: Couldn't decompress package" is thrown when importing a specific .unitypackage
How to reproduce:
1. Create an empty project
2. Import the attached "test.unitypackage"
3. Observe the Console Window
Expected result: No errors are thrown and the package is imported
Actual result: "Failed to import package with error: Couldn't decompress package" error is thrown
Reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.3f1, 2020.2.0a21
Note: Not reproducible on Windows
Comments (1)
-
nordicelectronics
Aug 19, 2020 20:09
This issue only happens using MacOS Mojave 10.14
When exporting a unitypackage that has files such as textures, fonts, sounds etc. that you have imported yourself, then the unitypackage will not import, not even in the same project you used to export the package.
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
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.1.0a1