Bug 6652 - Cannot debug app in an emulator in 4.2.4
Summary: Cannot debug app in an emulator in 4.2.4
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.2.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-08-22 15:00 UTC by Allie Miller
Modified: 2013-03-06 13:47 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Allie Miller 2012-08-22 15:00:28 UTC
Case #15778
When the "select Device" dialog pops up, customer attempts to  start the emulator, but after it is started and past the unlock screen it doesn't appear in the list of devices.

Has attempted adb kill-server / adb start-server does does *not* help anymore. Neither does killing the adb.exe process with the Windows Task Manager 

Debugging on a physical device still works.

Customer has double-checked that the path to the SDK is still set correctly.

Is using Mono for Android 4.2.4

Visual Studio 2010 ultimate SP1
Comment 1 Adrian Grigore 2012-08-22 15:09:43 UTC
Being said customer I'd like to add that the workaround to this problem (killing adb.exe) used to work fine on my computer before upgrading to Monodroid 4.2.4
Comment 3 PJ 2012-09-17 13:41:16 UTC
Heyo I think we might need some more information on this one. 


Is the emulator visible to adb? 

Aka, if you run:

adb devices

Does adb see the emulator?


A few other follow up questions: 

Does this happen with more than one emulator?
Are you using the AVDs generated by the Mono for Android install, or other ones?
If not, can you send the .ini for the corresponding AVD (so we can run the same emulator and check?)

Thanks!
Comment 4 Mikayla Hutchinson [MSFT] 2012-09-17 14:23:15 UTC
There are certain cases where adb doesn't detect device/emulators. This is fixed by restarting adb. More recent versions of the VS addon have switched to MonoDevelop's mechanism of maintaining a persistent connection to adb instead of polling, which improves performance, but means that when adb crashes or is killed, the connection is lost.

MonoDevelop has a "Refresh" button that restarts adb and reconnects to it, VS needs this too.
Comment 5 Dominique Louis 2012-09-25 17:28:39 UTC
A refresh buttons fix has been submitted to QA, so this will hopefully make it into the next Alpha release.
Comment 6 dean.ellis 2013-03-06 13:47:01 UTC
This fix with the refresh button has been released. This has been tested on developer machines and the refresh button works.