Search Issue Tracker
By Design
Votes
0
Found in
2017.4.1f1
Issue ID
1039298
Regression
No
[OSX] EditorApplication.Exit does not return a value when called in batch mode
To reproduce:
1. Open project
2. Open Terminal, change the location to a downloaded folder directory
3. Open unity_run.sh, change Unity path to a correct one
4. Run unity_run.sh
Expected: EditorApplication.Exit will return 0 to terminal
Actual: EditorApplication.Exit does not return any value, only external process launching is written to console(see attached image)
Reproduced: 5.6.5p1, 2017.1.4p2, 2017.2.3p1, 2017.3.2f1, 2017.4.6f1, 2018.1.7f1, 2018.2.0b10, 2018.3.0a3
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 warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
The problem seems to lie with the unity_run.sh script provided by the reproduction project.
The problem is that the OUTPUT variable copies the stdout from the process run, not the exit code.
To get the exit code, the variable $? should be used.