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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.