Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a13
2019.1.1f1
2019.2.0a1
Issue ID
1151883
Regression
Yes
On Standalone builds Player log is created when "Use Player Log" option is disabled
How to reproduce:
1. Create a new project on the Standalone platform
2. In Player Settings, uncheck the "Use Player Log" checkbox in "Resolution and Presentation" tab
3. Build and run the project
4. Check the projects log directory for "Player.log" ("\AppData\LocalLow\CompanyName\ProductName\Player.log")
Expected results: Player logs are no created
Actual results: Player logs are created
Reproducible with: 2019.1.0a13, 2019.1.1f2, 2019.2.0a7
Not reproducible with: 2017.4.26f1, 2018.4.0f1, 2019.1.0a12, 2019.2.0a8, 2019.2.0b1, 2019.3.0a2
Note:
Successfully reproduced the issue with both Windows and Mac machines
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 (fix version 2019.2):
Fixed in 2019.2.0a7