Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.2
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
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
- Dynamic Clipping works poorly with large scenes / terrains with the pivot point is near
- [UWP] Deploying wrong architecture through device portal ends up running a different app
- [MacOS] Standalone build contains .meta files inside native plugin bundles
- Progressive lightmapper leaks memory upon subsequent scene switches and bakes
- [AssetBundle] "The referenced script (Unknown) on this Behaviour is missing!" errors when loading object from Asset Bundle
Barkers-Crest
Sep 17, 2017 16:16
Is there a work around for this? This is a big blocker.