Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2017.4.32f1
2018.4
Issue ID
1196703
Regression
No
Building through batch mode fails if a script was deleted outside of the Editor
Reproduction steps:
1. Open and Exit "UnityIssue726318.zip" project
2. Delete any script (Advert.cs)
3. Run Unity with the command line arguments: "*EDITOR PATH*\Unity.exe -batchmode -nographics -quit -buildTarget ios -executeMethod ExternalBuildProcess.BuildiPhone -projectPath "*PROJECT PATH*" -logfile "*LOG PATH*\Log.log""
4. After the build completes, check the log
Expected Result: "ExitCode 0"
Actual Result: "ExitCode 1"
Reproduced with: 2018.4.13f1, 2017.4.35f1
Did not reproduce on: 2020.1.0a14, 2019.3.0b12, 2019.2.13f1
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note:
https://docs.unity3d.com/Manual/CommandLineArguments.html
The -executeMethod command line parameter says how to control the exit code from their script execution by manually calling EditorApplication.Exit with zero or non-zero. If this is not used, Unity returns the exit code based on the entire application sate.