Search Issue Tracker
Third Party Issue
Third Party Issue in 2022.2.X
Votes
0
Found in
2021.3.21f1
2022.2.12f1
Issue ID
UUM-31085
Regression
No
Cannot attach or debug the Player when using Rider IDE
Reproduction steps:
1. Open the attached “Repro.zip” project
2. Open the Build Settings window (File > Build Settings)
3. Enable the “Development Build”, “Script Debugging” and “Wait For Managed Debugger” options in the Build Settings window
4. Build the Player
5. Open the “Assets/Scripts/System/Control.cs” Script with Rider IDE
6. Set a breakpoint at the 317th line
7. Run the Player and attach the Rider Debugger to it
8. Try to step over the 317th line in the debugger
Expected result: Rider debugger steps over and advances further in the script
Actual result: Rider doesn’t advance and freezes as shown in RiderError.jpg
Reproducible with: 2021.3.21f1, 2022.2.12f1,
Couldn’t test with: 2020.3.47f1, 2023.1.0b9, 2023.2.0a7 (Script errors in the user’s project)
Reproducible on: M1 macOS 13.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
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
- MeshCollider preview gizmo disappears from the Scene view when overriding the mesh asset using any 3D editing tool
- Tutorial project is not created when started from the Get set up tab
- Audio Listener Component expands when selected
- [iOS] Frame Debugger rendering output doesn't work with iOS builds
Resolution Note:
This issue is corrected in JetBrains Rider 2023.1.1
Resolution Note (2022.2.X):
This issue is corrected in JetBrains Rider 2023.1.1