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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
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