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
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
Add comment