Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.3.0a1
2018.2.12f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1099724
Regression
No
"Debug.Log()" outputs file which is not relevant to the user when using IL2CPP scripting backend
Reproduction steps:
1. Create a New Project
2. Create a Script where there is a "Debug.Log()" printed when playing
3. Attach it to any GameObject
4. Build the project with IL2CPP scripting backend or with Mono (and delete the .pdb files)
5. Run the built project executable
6. Observe the Player.log message contains a message similar to (Filename: .... Runtime/Export/Debug/Debug.bindings.h Line: 35), which is irrelevant from the user's perspective
Expected Result: No irrelevant line is printed
Actual Result: Irrelevant line is printed
Reproduced with: 2019.2.0a5, 2019.1.0b3, 2018.3.5f1, 2017.4.20f1
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
Add comment