Search Issue Tracker
Third Party Issue
Third Party Issue in 2021.3.X
Votes
0
Found in
2021.3.5f1
Issue ID
UUM-29396
Regression
No
[Android] Breakpoints are stuck on "Evaluating" status and fail to retrieve information when debugging with Rider
How to reproduce:
1. Open the user’s attached “UCTemplateToReduced” project
2. Set a breakpoint at line 323 in the Assets/Script/Loading/GameController.cs script in the Rider
3. Toggle on the Android “Development Build”, “Script Debugging” and “Wait For Managed Debugger” build flags in the Build Settings
4. Build and Run
5. Attach the Unity process to the Rider
6. Hover with mouse over variable when breakpoint hits
Expected result: Object information is displayed
Actual result: Permanently “Evaluating” status is displayed
Reproducible with: 2021.3.5f1 (reporter’s info)
Couldn’t test with: 2020.3.46f1, 2021.3.20f1, 2022.2.11f1, 2023.1.0b6, 2023.2.0a5 (failing to attach Unity process to the Rider after countless retries)
Reproduced on: Windows 11 (reporter’s info)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This issue is corrected in JetBrains Rider 2023.1.1.
Resolution Note (2021.3.X):
This issue is corrected in JetBrains Rider 2023.1.1.