Debug mode and unit tests are both unable to hit breakpoints.

Hello,

Thank you for contacting JetBrains Support. I'm glad to work with you on this ticket. 

I have reviewed the logs you uploaded but didn't find any relevant exceptions. Additionally, I haven't identified any known issues in our tracker related to this problem.

Could you first try the following to revert Rider to its initial state and see if the issue persists? 

Clear Caches:

• Navigate to File → Invalidate Caches.
• Select Invalidate and Restart, then verify if the issue is resolved.

Delete .idea folder

.idea folder in solution folder contains project configurations specific to Rider. Please delete this folder to reset configurations, then restart Rider. A new default .idea folder will be generated. If you'd like to keep a backup, rename .idea folder to something else(e.g., .idea_backup). 

Disable All Downloaded Plugins:

• Go to Rider Settings → Plugins.
• Disable all downloaded plugins

• Restart Rider and check if the issue persists.

If the issue continues, please provide:

• Screenshots or a video recording of the issue.
• Information on whether this occurs with a specific project or all projects. If it's limited to a particular project, could you share a demo to help reproduce the issue? If that's not convenient, please provide more details about the project, such as the testing framework it uses, library versions, etc.

Regards,

Tom

This issue occurs in all projects, even newly created ones.

Additionally, the breakpoint shows the following message:

Line breakpoint

Didn’t find the associated module for the breakpoint /Users/poku/RiderProjects/AudioService_backend/ConsoleApp1/ConsoleApp1/Program.cs:3,1

Hello, 

Thanks for the information. To help us diagnose this issue, please provide the information below:

• Does the sample project newly created use the default console project template? If not, please share the project. 
• Go to Settings | Build, Execution, Deployment | Toolset and Build, ensure “.NET CLI executable path” is set correctly:

Please also share the screenshot of this setting page. 

• Collect full log bundle of Rider:

1. Go to Help | Diagnostic tools | Choose Trace Scenarios;
2. Enable the trace scenario for Debugger;
3. Reproduce the issue;
4. Collect the full log bundle via Help | Collect Logs and Diagnostic Data;
5. Disable the trace scenarios enabled;

Please upload the requested files to our upload server and share the ID.

Thanks,

Tom