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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Add comment