Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.1f1
Issue ID
1005679
Regression
No
Confusing errors are thrown when using "-importPackage" argument without providing a correct path to .unitypackage file
How to reproduce:
1. Acquire a Unity project
2. Execute this in terminal: "./Unity -projectPath /path/to/project -importPackage /random/path/"
(Leave out x.unitypackage file itself from the path. E.g., "./Unity -projectPath ~/project -importPackage ~/")
3. Observe the errors thrown in the Unity Console once Launched:
"Failed to import package with error: Couldn't decompress package"
"Failed importing package"
Expected result: an error is thrown, explaining that a .unitypackage file was not found in the provided file path
Actual result: errors thrown that are confusing for users:
"Failed to import package with error: Couldn't decompress package",
"Failed importing package"
Reproduced with: 5.5.6f1, 5.6.5p2, 2017.1.3p2, 2017.2.2f1, 2017.3.1p3, 2018.1.0b11, 2018.2.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment