Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2018.4.5f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1181994
Regression
No
Logs still include a Stack Trace after setting Application.SetStackTraceLogType to StackTraceLogType.None
How to reproduce:
1. Open tester-attached project (case_1181994-702390-Updated)
2. Open the 'MainScene'
3. Enter Play Mode
4. Open Editor.log and find the line "Exception: Test Exception"
Expected result: the Exception is not followed by a Stack Trace
Actual result: the Exception is followed by a Stack Trace
Reproducible with: 2017.4.32f1, 2018.4.8f1, 2019.2.5f1, 2019.3.0b3, 2020.1.0a3
Notes:
Setting Application.SetStackTraceLogType to None only affects Exceptions
Setting -stackTraceLogType None via a Command Line Argument not only affects exceptions: Logs, Assertions, Errors, Warnings and Exceptions continue to show full stack traces
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
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- "Add Component" button overlaps the Volume component UI when creating a new Volume Profile in a wide Inspector on high-DPI scaling
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
- UI counter displays incorrect collectible count when using "Remaining_Collectibles_UI" Prefab in "Get Started With Unity" template
- Camera Output Texture does not revert back to previously set Render Texture when camera selection in UI Builder canvas background is changed
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a11