Bug 15353 - Unable to debug in VS 2012 with 4.8.03015
Summary: Unable to debug in VS 2012 with 4.8.03015
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.8.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2013-10-11 10:17 UTC by Neal
Modified: 2013-11-21 03:12 UTC (History)
2 users (show)

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 for Bug 15353 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Neal 2013-10-11 10:17:37 UTC

I installed Xamarin.Android 4.8.03015 in Windows 8 Pro and I'm connected to my Samsung Galaxy S4 (Android 4.2.2) and the app launches then closes when trying to debug.  Otherwise the app runs fine.  I'm unable to debug on the device.  I have not tried an emulator as of yet as they are so painfully slow in Windows.

Comment 1 Nischal 2013-11-21 00:58:07 UTC
Today we have checked this issue with the following builds:

All windows
VS 2012/2013
MFA 4.10.01073

we are able to reproduce this issue with latest builds and already reported a issue for this :

Hence confirming this issue.