Unable to debug MAUI android source code as it contains the bug because VS 2022 cannot find source symbol files

[devhls]

Description

When I set breakpoint in the maui-android source code of the MAUI project I can't reach it because the following error is displayed:

No compatible code running on the thread.

The selected debug engine does not support any code executing on the current thread (e.g. only native runtime code is executing). You can switch to another thread to see if there is compatible code running

I did not test other platforms. Probably this does not work there too.

Steps to Reproduce

1.Open Microsoft.Maui.Controls.ContentPage. 2.Set a breakpoint in the class constructor. 3.Run android app in debug mode (emulator or local device wifi-debugging). 4.Open a content page.

Link to public reproduction project repository

No response

Version with bug

Unknown/Other

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Android

Did you find any workaround?

No, there is no clue after several days with it.

Relevant log output

No response

[github-actions[bot]]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Unable to hit debug point in C# Library from Android MAUI .NET7 App (#21323), similarity score: 0.78

Closed similar issues:

• Unable to debug native Android libraries (#9555), similarity score: 0.81
• [Bug] Breakpoints when debugging always point to external code (#2699), similarity score: 0.80
• Unable to debug android emulator (#3208), similarity score: 0.78
• Debugging issue from Visual studio 2022 preview 4.0 and 4.1 (#2629), similarity score: 0.77

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[dotnet-policy-service[bot]]

Thanks for the issue report @devhls! This issue appears to be a problem with Visual Studio, so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS.

If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

1. Go to the Visual Studio for Windows feedback tool or Visual Studio for Mac feedback tool to report the issue
2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

[dotnet-policy-service[bot]]

Thanks for the issue report @devhls! This issue appears to be a problem with Visual Studio (Code), so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS (Code).

If you encounter a problem with Visual Studio or the .NET MAUI VS Code Extension, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

1. Go to the Visual Studio for Windows feedback tool or .NET MAUI VS Code Extension repository to report the issue
2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

[drasticactions]

The MAUI UI Framework team does not maintain the debugger tooling, it's maintained by the Visual Studio team. If you ask there, they could help you out.

[beefydog]

Just started to happen to me. Code, unchanged, ran just fine yesterday, now this! dead in the water