Out of curiosity, I tried again to debug on my old Samsung Tab A. It failed with the following
Found device: 2a3ee81a22bb42a6
Installing Package com.companyname.navigationgraph7net7
Installed Package com.companyname.navigationgraph7net7. [87799ms]
XA0137: The 'run-as' command failed with 'run-as: Could not set capabilities: Operation not permitted
'.
Fast Deployment is not currently supported on this device.
Please file an issue with the exact error message using the 'Help->Send Feedback->Report a Problem' menu item in Visual Studio
or 'Help->Report a Problem' in Visual Studio for Mac.
Please set the 'EmbedAssembliesIntoApk' MSBuild property to 'true' to disable Fast Deployment in the Visual Studio project property pages, or edit the project file in a text editor.
Done executing task "FastDeploy" -- FAILED.
Done building target "_Upload" in project "NavigationGraph7Net7.csproj" -- FAILED.
Done building project "NavigationGraph7Net7.csproj" -- FAILED.
Build FAILED.
1>Deployment failed to Samsung SM-T350.
1>Deploy failed
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Elapsed 01:34.561 ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
========== Elapsed 01:34.561 ==========
That was similar to what I used to get. If I then change to a release build the app installs and runs fine on that device.
I then tested with Fast Deployment disabled by adding the following to the .csprog file
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
<EmbedAssembliesIntoApk>True</EmbedAssembliesIntoApk>
</PropertyGroup>
I could then debug normally, hitting breakpoints, stepping etc. However, the deployment time went way up. You'd need a lot of patience to work all day with fast deployment turned off. I'm not sure if I turned off fast deployment when I tried last time so I can't confirm, but I presume I did at least try it.
The other difference is that the particular app I tried it with has been converted to net7.0-android, so I can't confirm that it would work with a typical xamarin.android app. I'm using VS 2022 17.5.0 Preview 1.0