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
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
- LocalizationSettings.InitializationOperation hangs when re-entering Play Mode with Domain Reload disabled
- [UI Toolkit] Delete key deletes the incorrect character and allows for an extra character deletion when language direction is set to RTL
- Dropdown property is cut off and adds unnecessary side padding when a Sub Graph is used as a node in Shader Graph
- All text in the Project Settings Window is still Tinted White after deleting Text in the Search Window
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.