Bug 2476 - A pop up with 'Force close' displayed on emulator while debuging Application
Summary: A pop up with 'Force close' displayed on emulator while debuging Application
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-12-13 07:53 UTC by Saurabh
Modified: 2016-08-03 15:37 UTC (History)
6 users (show)

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

Debug (355.13 KB, image/png)
2011-12-13 07:53 UTC, Saurabh

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 Saurabh 2011-12-13 07:53:33 UTC
Created attachment 1039 [details]

Steps to reproduce:
1.Launch MonoDevelop.
2.Open Application 'HelloWorld'
3.Debug application on API10.
4.Verify that Emulator displayed popup with 'Force close'

Expected result:
Application should be run successfully in debug mode on emulator.

Actual result:
When user debug the application on emulator.popup with 'Force Close' displayed 

Test data :
Please refer attached screenshot

Error details:
System.IO.IOException: DWP Handshake failed.
  at Mono.Debugger.Soft.Connection.Connect () [0x000f9] in /private/tmp/source/monodevelop/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/Connection.cs:1058 
  at Mono.Debugger.Soft.VirtualMachine.connect () [0x00000] in /private/tmp/source/monodevelop/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/VirtualMachine.cs:296 
  at Mono.Debugger.Soft.VirtualMachineManager.Connect (Mono.Debugger.Soft.Connection transport, System.IO.StreamReader standardOutput, System.IO.StreamReader standardError) [0x00022] in /private/tmp/source/monodevelop/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/VirtualMachineManager.cs:334 
  at Mono.Debugger.Soft.VirtualMachineManager.ConnectInternal (System.Net.Sockets.Socket dbg_sock, System.Net.Sockets.Socket con_sock, System.Net.IPEndPoint dbg_ep, System.Net.IPEndPoint con_ep) [0x00075] in /private/tmp/source/monodevelop/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/VirtualMachineManager.cs:287 

Mac lion
MonoDevelop 2.8.5
Mono for Android 4.0.1
Comment 1 Eric Beisecker 2011-12-13 11:34:54 UTC
Could not Reproduce on :

OS X Lion
MonoDevelop 2.8.5
Mono 2.10.6
Mono for Android 4.0.1
Comment 2 Jatin 2011-12-15 05:58:05 UTC
This issue still exists on:

OS X Lion
MonoDevelop 2.8.5
Mono 2.10.7 (Beta)
Mono for Android 4.0.1

Hence, reopening this issue.
Comment 3 PJ 2013-05-13 17:45:22 UTC
This happens because of the Hello app's 'long running process' test, which makes android believe it's not responding.

This app is now fully tested in automation, so RESOLVING as FIXED.