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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment