Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.11f1
2019.3
2020.1
Issue ID
1198027
Regression
No
[macOS] An exception catchpoint can't be created when catching non-System exceptions in Visual Studio
How to reproduce:
1. Open the user attached project
2. Open the 'Test' script in Visual Studio
3. Attach the debugger to Unity
4. In the Breakpoints tab in Visual Studio, click on "New Exception Catchpoint"
5. Select "When an exception is thrown" radio button
6. Type in "TestException" or "Unity" in the text field below the radio button
Expected results: Custom exception and the Unity exception is on the list
Actual results: Only System exceptions are listed
Reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.2.13f1, 2019.3.0b12, 2020.1.0a14
Visual Studio version: 8.3.8
Additional notes:
1. The issue does not reproduce on Windows 10 with Visual Studio Community 2019 ver. 16.2.3
2. The issue does not reproduce with Rider
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
- A 404 page is opened when selecting "Open Documentation" on the Float Node in Shader Graph
- Shader Graph Importer's Documentation Reference button leads to a 404 page
- Crash on WriteParticleLineVertex when particle systems are rendered in a specific project
- Asset names longer than the allowed system file path are not handled gracefully
- Moving VFX Particles leave a ghosting trial in Ray Traced Screen Space Reflections
Resolution Note:
This Visual Studio for Mac issue should be reported to Microsoft, as we just bundle Visual Studio for Mac with Unity and do not maintain it.