Unable to start debug session on the Android emulator when airplane mode is enabled.

[MaxxDelusional]

Description

When I try to debug my Maui Android app in Visual Studio, I am unable to launch the app on the Android emulator when the emulator is in Airplane Mode.

On the emulator, I can see my app launch with the default splashscreen (purple with .Net label), but it never gets past this point. In the debug output, I can see that it stops at this line.

[monodroid-debug] Trying to initialize the debugger with options: --debugger-agent=transport=dt_socket,loglevel=0,address=10.0.2.2:59908,embedding=1,timeout=1722005134

Disabling airplane mode when the app is in this hung state will allow the debugger to continue, and the app will launch as expected.

My Emulator has the following specs:

• API: 33
• OS: Android 13.0
• Processor: x86_64
• Memory: 1GB
• Google APIs: Included

Steps to Reproduce

• Launch the Android Emulator
• Put the emulator in Airplane mode
• Create a new .Net MAUI App
• Set the build target to be the running emulator
• Press F5 to start a debug session

Expected:

Default (Click me) app to launch on the Android emulator with debugger attached.

Actual:

App launches on Android emulator but is stuck on splash screen.

Link to public reproduction project repository

No response

Version with bug

8.0.61 SR6.1

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

No response

Did you find any workaround?

Airplane mode can easily be toggled from the ADB command prompt with the following commands.

adb shell cmd connectivity airplane-mode disable
adb shell cmd connectivity airplane-mode enable

This makes it a bit easier to ensure that airplane mode is disabled before debugging, but it's still not a complete solution. The app should be able to launch when airplane mode is disabled.

Relevant log output

No response

[github-actions]

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!

Closed similar issues:

• Starting the debugger with WiFi and Mobile Data turned off crashes (#7189), similarity score: 0.79
• unable to debug android apps on Linux (#23472), similarity score: 0.73
• This problem is easy to occur when debugging the real machine in VS17.9.3+Maui8.0.10, which is stuck all the time, and the phone does not have an application installed. VS17.9.3+Maui8.0.7 is normal. (#21247), similarity score: 0.73
• Unable to debug android emulator (#3208), similarity score: 0.73
• Cannot debug .NET MAUI Android project on real Android physical device (#9159), similarity score: 0.73

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

[ninachen03]

This issue has been verified using Visual Studio 17.11.0 Preview 5 (8.0.70 & 8.0.61 & 8.0.3). Can repro it.

[MaxxDelusional]

This issue is bigger than I had originally realized.

At first, I thought airplane mode was only preventing the app from launching on the emulator, but with further testing, I can see that the debugger does not work at all when the emulator is in airplane mode.

This makes it impossible to debug offline scenarios using the emulator.

[jpobst]

.NET for Android debugging works over networking protocols to establish a connection between the app and the IDE. As such, an active network connection is required.

The only way to debug an offline scenario will be the classic "add logging and read the logs" method.