Bug 51797 - android debugger disconnects
Summary: android debugger disconnects
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-01-26 19:21 UTC by Andrew
Modified: 2017-01-28 06:29 UTC (History)
3 users (show)

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


Attachments
application output (8.31 KB, text/plain)
2017-01-26 19:53 UTC, Andrew
Details
log files (584.45 KB, application/zip)
2017-01-26 19:53 UTC, Andrew
Details
buildLog1.txt (120.30 KB, text/plain)
2017-01-26 21:49 UTC, Andrew
Details


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 51797 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:
Status:
CONFIRMED

Description Andrew 2017-01-26 19:21:55 UTC
=== Xamarin Studio Enterprise ===

Version 6.1.5 (build 0)
Installation UUID: c6cc2bf2-3d75-4e51-bb1f-b12a2a84f591
Runtime:
	Mono 4.6.2 (mono-4.6.0-branch/ac9e222) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 406020016

=== NuGet ===

Version: 3.4.3.0

=== Xamarin.Profiler ===

Version: 1.0.2
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 8.2.1 (11766.1)
Build 8C1002

=== Xamarin.Mac ===

Version: 2.10.0.120 (Visual Studio Enterprise)

=== Xamarin.Android ===

Version: 7.0.2.42 (Visual Studio Enterprise)
Android SDK: /Users/mccorma/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)
		7.0    (API level 24)

SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.3
SDK Build Tools Version: 25.0.2

Java SDK: /usr
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin Android Player ===

Not Installed

=== Xamarin.iOS ===

Version: 10.3.1.8 (Visual Studio Enterprise)
Hash: 7beaef4
Branch: cycle8-xi
Build date: 2016-12-20 02:58:14-0500

=== Build Information ===

Release ID: 601050000
Git revision: 7494718e127af9eaec45a3bd6282d3da927488bd
Build date: 2017-01-17 10:31:01-05
Xamarin addins: c92d0626d347aaa02839689eaac2961d24c9f446
Build lane: monodevelop-lion-cycle8

=== Operating System ===

Mac OS X 10.11.6
Darwin ITM-mccorma-f8j8.local 15.6.0 Darwin Kernel Version 15.6.0
    Mon Jan  9 23:07:29 PST 2017
    root:xnu-3248.60.11.2.1~1/RELEASE_X86_64 x86_64

=== Enabled user installed addins ===

Gorilla Player 0.9.1.2
Comment 1 Andrew 2017-01-26 19:26:40 UTC
This has been going for for months with several version of XS on the Mac.   Reply with what you like me to provide to troubleshoot this problem.

Problems.

1.  It takes 3-5 times to run the app on an attached device.  1-4 times I get a message saying "deployment completed" and nothing is running.  I need to hit the run button another several times to get it to run on the device.

2.  the debugger disconnects from the device after a few screens are rendered. I have a breakpoint and XS stops there, but after that the debugger decides to disconnect.  Sometimes the debuggers works for longer and other times it stops running with or without breakpoints.

3.  a few other times I get error deploying or device not connected errors but I hit run again and it works.
Comment 2 Andrew 2017-01-26 19:27:42 UTC
Here one build error.  

Deploying package to '04157df493b1433e'

Detecting installed packages

Deployment failed because of an internal error: Address already in use

Deployment failed. Internal error.


I hit run again and it works.  Nothing else is using the device.
Comment 3 Andrew 2017-01-26 19:53:01 UTC
Created attachment 19497 [details]
application output
Comment 4 Andrew 2017-01-26 19:53:50 UTC
Created attachment 19498 [details]
log files
Comment 5 Andrew 2017-01-26 21:35:37 UTC
Deploying package to '04157df493b1433e'

Detecting installed packages

Waiting for packaging to complete

Removing previous version of application

Installing application on device

Synchronizing assemblies

Synchronizing native libs

Synchronizing dexes

Synchronizing assemblies

Deployment failed due to an error in FastDev assembly synchronization.

Deployment failed. Assembly synchronization error.
Comment 6 Andrew 2017-01-26 21:49:18 UTC
Deploying package to '04157df493b1433e'

Detecting installed packages

Waiting for packaging to complete

Synchronizing assemblies

Synchronizing native libs

Synchronizing dexes

Synchronizing resources

Synchronizing resources

Deployment completed


** NO DEPLOYMENT **  Upload build log (BuildLog1.txt)
Comment 7 Andrew 2017-01-26 21:49:54 UTC
Created attachment 19502 [details]
buildLog1.txt
Comment 8 David Karlaš 2017-01-28 06:29:31 UTC
Based on log files this seems Android specific, hence moving to Android.