Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0a8
2019.4
2019.4.15f1
2020.2
Issue ID
1296096
Regression
Yes
[macOS] No messages are printed in the Terminal when launching Editor in the Batchmode
How to reproduce:
1. Download and extract the attached project "TerminalLogBug.zip"
2. Open the Mac Terminal
3. In Terminal, write "/Applications/<Path to Unity>/Unity.app/Contents/MacOS/Unity -projectPath <Path to Project> -executeMethod DummyTerminal.BuildDummyTermimal -batchmode -exit -buildTarget ios -logFile <Path to Output>"
4. Observe the Terminal output
Expected result: Editor outputs to the Terminal Window
Actual result: Editor doesn't output to the Terminal Window
Reproducible with: 2019.3.0a8, 2019.4.18f1, 2020.2.1f1
Not reproducible with: 2018.4.30f1, 2019.2.21f1, 2019.3.0a7, 2020.2.2f1, 2021.1.0b2, 2021.2.0a1
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2020.2):
Fixed in Unity 2020.2.2f1 and above