Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.2.X
Votes
1
Found in
2017.2.0b11
Issue ID
949806
Regression
Yes
[UWP] - 2017.2 - Breakpoints do not get hit with Debug/Release configurations when debugging
Steps to reproduce:
1. Open attached project "949806.zip"
2. Build for UWP with .NET scripting backend
3. Open VS solution
4. Open "Test.cs" and insert a new breakpoint
5. Deploy on local machine with either Debug or Release configuration
Actual result: breakpoints do not get hit
Not reproducible with Master configuration
Reproducible with: 2017.2.0b11
Not reproducible with: 2017.1.f1, 2017.3.0a7
Comments (1)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Barkers-Crest
Sep 17, 2017 16:16
Is there a work around for this? This is a big blocker.