Search Issue Tracker
Fixed
Votes
0
Found in
2018.4
2018.4.30f1
Issue ID
1297000
Regression
No
[Windows] Editor doesn't exit after making a build in Batch-mode when using a "quit" parameter and logging to file
How to reproduce:
1. Download and extract the attached project "case_1297000-Project.zip"
2. Open up a command prompt window
3. Write the following command: <Path to Unity>\Unity.exe -quit -batchMode -buildTarget WebGL -projectPath <Path to Project>
-executeMethod "BuildScript.BuildRelease" -silent-crashes -logFile <Path to Output>
4. Wait for the build process to finish
5. Open up the outputted log file
6. Inspect the end of the log
Expected result: Batch mode quit successfully
Actual result: Editor doesn't quit
Reproducible with: 2018.4.30f1
Not reproducible with: 2019.1.0a1, 2019.4.18f1, 2020.2.2f1, 2021.1.0b2, 2021.2.0a2
Note: Not reproducible on Mac
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note:
Fixed in Unity 2019.1.0a1 and above