Search Issue Tracker
By Design
Votes
0
Found in
2021.3.36f1
2022.3.21f1
2023.3.0b10
6000.0.0b11
Issue ID
UUM-66689
Regression
No
Debug messages are not synced back to the Editor when running the Editor in batch mode and building the project
How to reproduce:
1. Open the attached “BatchmodeLogMessageTest.zip” project in batch mode with the following command line arguments (if reproducing on macOS): ”[UNITY PATH] -batchMode -forgetProjectPath -logFile [“BatchmodeLogMessageTest” PATH]/log_b.log -runTests -projectPath [“BatchmodeLogMessageTest” PATH] -testResults [“BatchmodeLogMessageTest PATH]/results_b.xml -testPlatform StandaloneOSX”
2. Open the “log_b.log“ text file in the project’s folder
3. Search for "Debug.Log"
Expected result: “Debug.Log“ messages exist and can be found
Actual result: “Debug.Log“ messages don’t exist and can’t be found
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0b3
Reproducible on: macOS 14.2.1 Sonoma (Intel)
Not reproducible on: No other environment tested
Notes:
- To reproduce this issue on Windows change “-testPlatform StandaloneOSX“ to “-testPlatform StandaloneWindows64”
- If the “-batchMode“ command line argument is removed when adding the arguments, the generated “log_b.log“ will have “Debug.Log“ messages
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Resolution Note:
The only reason you see the player log when not applying batch mode is because of a technicality of how the Console window works in the editor. You can sort of tell by the format of the log messages where there are UI markers in the message.
If you would run an editor instance where you have closed the Console window you would also not see the player log message in the editor log.
If you want to try this out yourself, you can reproduce this by launching the project in the editor, close the console window and then go back to command line and run tests without `-batchMode`.