Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2020.3.19f1
2021.1
2021.2
2022.1
Issue ID
1375776
Regression
No
Unity terminates with error code 0 when an exception occurs while importing a package in bach mode
Steps to reproduce:
1. Create an empty project, then close it
2. Download and extract the attached "somePackage.unitypackage" into the created project's folder
3. Open Terminal/Windows Command Prompt and navigate to the Editor location
4. Launch Unity Editor with the following command-line arguments: "Unity.exe -batchmode -nographics -quit -logfile "<project_pathname>\editor.log" -projectPath "<project_pathname>" -importPackage "<project_pathname>\somePackage.unitypackage""
5. Open editor.log in the project's folder and scroll to the bottom of the file
Expected result: last lines read "Scripts have compiler errors. Exiting without the bug reporter. Application will terminate with return code 1"
Actual result: the last line reads "Exiting without the bug reporter. Application will terminate with return code 0"
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.1.28f1, 2021.2.1f1, 2022.1.0a13
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
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- Crash on RebuildTransformHierarchyOrMarkForDestruction when opening a scene
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a3
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b7
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.11f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.28f1