Search Issue Tracker
Active
Under Consideration for 3.0.X
Votes
0
Found in [Package]
3.0.6
Issue ID
RIDER-29
Regression
Yes
IDE fails to attach to the Unity Process when reenabling Debug mode in the Editor
How to reproduce:
1. Open the user attached "DebugTest.zip" project
2. Enter the "SampleScene" Scene
3. Open the "Test.cs" Script with Rider
4. Add a Breakpoint to the line containing the Debug.Log command
5. Return to the Editor and turn on Debug Mode
6. Press Play
7. Return to the IDE and Attach the Unity Process (Run -> Attach to Unity Process)
8. Stop Debugging in the IDE and return to the Editor
9. Exit Play Mode
10. Disable and re-enable the Debug Mode
11. Return to your IDE and re-attach the Unity Process
Expected result: The Unity Process is attached successfully
Actual result: "Unable to connect to Unity" is thrown in the IDE
Reproducible with: 3.0.6, 3.0.12 (2021.2.0a18, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5)
Not reproducible with: 3.0.5, 3.0.6, 3.0.12 (2020.3.30f1, 2021.2.0a15)
Couldn't test with: 2019.4.36f1 (No Debug button), 2021.2.0a16, 2021.2.0a17 (Debug button does not open)
Note:
- Reproducible with Visual Studio and Rider
- Visual Studio Code throws "No Unity Process Found" (Cannot test)
- Reproducible with a new project
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
- GPU usage doubles when a project is running in the background
Add comment