Cannot debug .NET MAUI Android project on real Android physical device

[yschang]

Description

I want to develop a MAUI-App and debug it on my local Android device. I've followed this documentation - https://github.com/Sweekriti91/ArtAuction/blob/maui-projecthead/ArtAuction.Android/ArtAuction.Android.csproj
And tried running the app on my local Android device, but I'm only able to start a simulator. I see that my Android device is connected from "Android Local Devices", but I'm not sure how to start debugging on my phone. I had no trouble debugging on my local device when I was developing Xamarin, but now I'm having this trouble when developing .NET MAUI.

Steps to Reproduce

1. Connected my Android device via USB cable.
2. Followed doc from https://github.com/Sweekriti91/ArtAuction/blob/maui-projecthead/ArtAuction.Android/ArtAuction.Android.csproj
3. Added <EmbedAssembliesIntoApk>true</EmbedAssembliesIntoApk> and rebuild Android project.

Version with bug

6.0 Release Candidate 2 or older

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Android 12

Did you find any workaround?

No, I tried Wi-Fi debugging, but gave me the same error

Relevant log output

N/A

[jfversluis]

Without any error message or logs it will be impossible to diagnose this. Also, this is probably more of a tooling issue/question. Be sure to check out the build/deployment output windows and see if there is any more information in there. You probably want to try opening a discussion or maybe ask your question on Stack Overflow or if you think if there is an issue open one on the Visual Studio feedback portal, the link will be down below.

[ghost]

Thanks for the issue report yschang! 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 VS 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.

This issue will be automatically closed in 3 days if there are no further comments.

[yschang]

Without any error message or logs it will be impossible to diagnose this. Also, this is probably more of a tooling issue/question. Be sure to check out the build/deployment output windows and see if there is any more information in there. You probably want to try opening a discussion or maybe ask your question on Stack Overflow or if you think if there is an issue open one on the Visual Studio feedback portal, the link will be down below.

Thanks for the follow up. I did not see any log from the build output window, but I did see the following log from the deployment output window:

`IsEmulatorSupported: START
	Is64BitOperatingSystem = True
DetectSlat: START
	isHyperVRunning = False
	isHardwareVirtualizationSupported = True
	isHardwareVirtualizationEnabledInBIOS = False
DetectSlat: END (Success, 0:00:02.267)
	SlatState = SlatAndHWVDisabled
	IsEmulatorSupported = True
IsEmulatorSupported: END (Success, 0:00:02.452)

`
Not sure if this helps at all. I will post this question on Visual Studio feedback portal.

[ghost]

This issue is being closed due to inactivity. If this issue is still affecting you, please follow the steps above to use the VS Feedback Tool to report the issue.