Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2017.3.0a1
2018.2.0a1
2018.2.6f1
2018.3.0a1
2019.1.0a1
Issue ID
1091616
Regression
No
Editor resumes when re-enabling breakpoint while debugging in Visual Studio Code
Steps to reproduce:
1. Open users attached project
2. Go to Edit -> Preferences -> External Tools -> External Script Editor and change it to Visual Studio Code
3. Open up "ScriptA.cs"
4. Add a breakpoint at line 7
5. Start debugging with Visual Studio Code
6. Add a breakpoint at line 8
7. Remove and re-add a breakpoint at line 8
Expected result: Unity Editor does not resume.
Actual result: Unity Editor resumes, even if breakpoint on line 7 is still present.
Reproduced in 2017.4.17f1, 2018.2.20f1, 2018.3.0f2, 2019.1.0a12
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
- Visible instance buffer returns 0 for every instance when using BatchDrawCommandIndirect on Adreno devices with Vulkan API
- [Android][Vulkan] Native crash in AndroidVulkanVideo::ProcessFrame and AndroidVulkanVideo::Context::~Context() when switching screens
- Screen brightness is not set to a default value when Screen.brightness is set to a negative value
- macOS app window title is not localized when built from generated Xcode project
- Unity Hub doesn't preserve the changed Channel when manually restarting the Hub
Resolution Note:
Unity has so far not been able to support it. There is no reason to believe that we will get to this in the near future.