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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Barkers-Crest
Sep 17, 2017 16:16
Is there a work around for this? This is a big blocker.