Search Issue Tracker
By Design
Votes
2
Found in
5.2.3p2
Issue ID
751500
Regression
Yes
changes to defined symbol list field (UI) are not detected in some scenarios
Reproduction steps:
1. Open attached "PostProcessBug" Unity project.
2. Open "Edit > Project Settings > Player"
3. Notice, that "Other Settings > Configuration > Scripting Define Symbols" input box is empty.
4. Build this project.
5. Notice the message in the console window in the editor, that says - "IS DEBUG!!"(There is a script, that checks if debug is defined).
Regression introduced in 5.1
Comments (1)
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
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
- Scaled Backgrounds List and dropdown text are enabled while Scaled Backgrounds field is disabled in IMGUI Debugger window
- Editor crashes when large value is entered in Scaled Backgrounds field of IMGUI Debugger window
- "Custom Function" Node "Input" type changes do not immediately show mistmatch errors when set to an incompatible type in Shader Graph
- My Assets list is populated with Asset Packages when setting how many Packages to display before clicking the Load button
scadieux
Feb 05, 2016 00:40
Actually Unity decided for some reason it was a good idea to define DEBUG and TRACE for non developer builds: https://unity3d.com/unity/whats-new/unity-5.1