Bug 40285 - Unable to sustain a Debugging session with an Android Phone using Xamarin Studio
Summary: Unable to sustain a Debugging session with an Android Phone using Xamarin Studio
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- critical
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2016-04-11 19:42 UTC by Hino
Modified: 2016-04-12 15:11 UTC (History)
4 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 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:

Description Hino 2016-04-11 19:42:02 UTC
# Steps to reproduce
#* Connect Android Device to Mac via USB connection
#* Hit the Play Button on the top left corner of Xamarin Studio

# Expected behavior
#* After the app has been deployed to the device, I get the following error: "The connection with the debugger has been lost."

# Actual behavior
#* As a Developer, I should see my debug session sustain

# Supplemental info (logs, images, videos)
#* This happens often with our BrivoPass and Brivo Mobile OnAir applications
#* Devices include: Nexus 6 and Nexus 5X (both on Android M)

# Test environment (full version information)
#* Xamarin Studio 5.10.3 (build 51)
Comment 1 Marek Habersack 2016-04-12 10:11:04 UTC
It's hard to tell without any logcat output, but I suppose it might be a duplicate of bug #35739 - please try to upgrade to the upcoming Alpha release of Xamarin.Android to see if the issue goes away.
Comment 2 Hino 2016-04-12 13:44:10 UTC

Thank you for your prompt response.  I have switched to the Alpha channel and my first debug session is going well.  I will observe and see if this performance holds on for the duration of the day.

Comment 3 Hino 2016-04-12 15:11:21 UTC

As you suggested, moving to the Alpha Channel to download the latest Xamarin.Android has helped with the problem.