Search Issue Tracker
Active
Under Consideration for 2022.2.X, 2023.1.X, 2023.2.X
Votes
0
Found in
2022.2.12f1
2023.1.0b10
2023.2.0a9
Issue ID
UUM-31871
Regression
Yes
Breakpoints are not working in embedded packages when using Visual Studio
Reproduction steps:
1. Open the attached "repro_IN-36580Breakpoints.zip" project
2. Open "Assets/Scenes/Main" Scene
3. Open scripts "Packages/Package Test/EmbeddedPackageBreakpoint.cs" and "Assets/Scripts/AssetFolderBreakpoint.cs" in Visual Studio 2022
4. Set breakpoints in line 13 of "Packages/Package Test/EmbeddedPackageBreakpoint.cs" and line 10 of "Assets/Scripts/AssetFolderBreakpoint.cs"
5. In Visual Studio press the "Attach to Unity" button
6. Enter Play mode in Unity
7. In Visual Studio press the "Continue" button and observe the breakpoints
Expected result: The script stops at the breakpoint in line 13 of the file "EmbeddedPackageBreakpoint.cs" and in line 10 of the file “AssetFolderBreakpoint.cs”
Actual result: The script stops only in line 10 of the file “AssetFolderBreakpoint.cs”
Reproducible with: 2022.2.1f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a9
Not reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.0f1
Reproducible on: Windows 10
Reproducible with code editors: Visual Studio Community 2022 17.5.1, Visual Studio Community 2019 16.11.25
Not reproducible with code editors: Rider 2022.3.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment