Search Issue Tracker
Not Reproducible
Votes
2
Found in
2019.4
2019.4.6f1
2020.1
2020.2
2021.1
Issue ID
1267825
Regression
No
[Linux] Build process does not shut down after completing successfully when building through the command line
Reproduction steps:
1. Download the FPS Microgame project through Unity Hub
2. Open it, then close and save the project
3. Build the project through the command line
Expected result: The build succeeds and the process is closed
Actual result: The build succeeds, but the process is not closed and gets stuck on the message "Batchmode quit successfully invoked - shutting down!"
Reproducible with: 2019.4.18f1, 2020.1.17f1, 2020.2.2f1, 2021.1.0b2
Could not test with: 2018.4.30f1 (due to errors when importing project)
Notes:
- Tested on Ubuntu 18.04
- To build through the command line, this command was used:
/Path/To/Unity -batchmode -nographics -quite -projectPath /Path/To/Project -buildLinux64Player /Path/To/Directory
- This issue seems to not be consistent. Different projects might not reproduce the issue at all or reproduce it at a different pace.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Antoine_Dezarnaud_Epnp
Apr 21, 2021 08:01
We launch the build as follow :
"$pathToUnity" -batchmode -nographics -quit -projectPath "$sourceFolder" -executeMethod EditorTools."$finalMethodName"
Unity launches an editor c# method that launches the build.
Antoine_Dezarnaud_Epnp
Feb 05, 2021 08:52
Encountered this bug too with 2019.4.18f1.
It's really blocking our company's delivery pipeline