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
- Different build sizes between Editor build and command-line build when "Static Batching" is enabled
- Particle System "Start Rotation" property affects a different axis when upgrading to newer Editor versions
- "Light" Component's "Culling Mask" setting is hidden but still has an effect when using HDRP
- Selecting the Web platform can be done when using the HDRP project
- Textures swap when SpriteRenderers with shared materials and animators are toggled on and off
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.