Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2017.3.1p1
Issue ID
1005744
Regression
No
[.NET 4.6] Cannot see local variables in VS Watch window when debugging async methods
Steps to reproduce:
1. Download attached project and open "Example" scene
2. Open script Example.cs in Visual Studios
3. Add breakpoint at line 11 and attach it to Unity
4. Enter play mode in Unity
5. When breakpoints trigger in VS Watch window type two local variables X and Y
Expected results: X or Y value is printed in Watch window Value column
Actual results: Instead of X or Y value error is printed "The identifier `y` is not in the scope"
Reproduced with: 2018.1.0b9, 2017.3.1p2, 2017.2.2f1, 2017.1.3p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment