Bug 11955 - Debugger does not attach to Android emulator
Summary: Debugger does not attach to Android emulator
Status: CLOSED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 3.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Vinicius Jarina
URL:
Depends on:
Blocks:
 
Reported: 2013-04-25 02:07 UTC by ronald.schellekens
Modified: 2015-01-19 05:31 UTC (History)
4 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 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:
CLOSED FIXED

Description ronald.schellekens 2013-04-25 02:07:28 UTC
VS2012 with update 2 with Resharper does not attach the debugger to the emulator when debugging starts. 

Package gets deployed but when trying to start the debugger stops and the session ends.
Running the same code from Xamarin Studio starts a debug session
Comment 1 Miguel de Icaza [MSFT] 2013-05-22 15:03:13 UTC
Vinicius, is there some log we could request from Ronald to see what is going on?
Comment 2 Parmendra Kumar 2015-01-16 12:48:55 UTC
@ronald I have checked this issue but I am not able to reproduce this issue at my end.
Could you please recheck this issue on latest build and let we know if you getting same behavior?
Comment 3 ronald.schellekens 2015-01-19 01:08:57 UTC
We are not using Xamarin anymore due to pricing issues.
Comment 4 Parmendra Kumar 2015-01-19 05:31:02 UTC
I have checked this issue and now its working fine. So I am closing this issue.