Bug 18882 - ios Simulator disconnects while running app.
Summary: ios Simulator disconnects while running app.
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.10.x
Hardware: PC Windows
: Normal normal
Target Milestone: 4.0.0 (C6)
Assignee: vsx
URL:
Depends on:
Blocks:
 
Reported: 2014-04-08 22:53 UTC by curtis.harrison@wavetronix.com
Modified: 2015-09-24 08:37 UTC (History)
5 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:
RESOLVED NOT_REPRODUCIBLE

Description curtis.harrison@wavetronix.com 2014-04-08 22:53:41 UTC
Description of Problem:
When debugging my app from Visual Studio to the iPad Simulator, the debugger stops without me telling it to.  This happens about 50% of the time.

Steps to reproduce the problem:
1. Open a project in Visual Studio 2013
2. Select iPhoneSimulator and iPad 7.1 as the Target iOS device
3. Click the 'Start' button to start debugging in Visual Studio
4. After the app has run for a few seconds, notice that the Visual Studio debugger has stopped
   and the iOS iPhoneSimulator is still running the app.


Actual Results:
Visual Studio debugger stops, as if I pressed the 'Stop' button.  The following appears in the output window:

Debug session started...
Loaded assembly: /Users/curtis/Library/Application Support/iPhone Simulator/7.1/Applications/47466B7C-FC4E-45C3-8431-57ADEC64A462/ADayBDayiOS.app/monotouch.dll [External]
Loaded assembly: /Users/curtis/Library/Application Support/iPhone Simulator/7.1/Applications/47466B7C-FC4E-45C3-8431-57ADEC64A462/ADayBDayiOS.app/System.Core.dll [External]
Loaded assembly: /Users/curtis/Library/Application Support/iPhone Simulator/7.1/Applications/47466B7C-FC4E-45C3-8431-57ADEC64A462/ADayBDayiOS.app/System.dll [External]
Thread started:  #2
Loaded assembly: /Users/curtis/Library/Application Support/iPhone Simulator/7.1/Applications/47466B7C-FC4E-45C3-8431-57ADEC64A462/ADayBDayiOS.app/ADayBDayiOS.exe
Loaded assembly: /Users/curtis/Library/Application Support/iPhone Simulator/7.1/Applications/47466B7C-FC4E-45C3-8431-57ADEC64A462/ADayBDayiOS.app/System.Xml.dll [External]
Loaded assembly: /Users/curtis/Library/Application Support/iPhone Simulator/7.1/Applications/47466B7C-FC4E-45C3-8431-57ADEC64A462/ADayBDayiOS.app/TimesSquare.iOS.dll
The program 'Mono' has exited with code 0 (0x0).
Getting device...
Starting debug on:iPad 7.1
Launching Application for debugging...
Starting debug session...
Debugging session ended.
Mono.IOS.VisualStudio.MonoTouchPackage Error: 0 : MonoTouchDebuggerSession
Mono.Debugging.Soft.ConnectionException: Could not connect to the debugger. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.1.92:55200

Server stack trace: 
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at Mono.Debugger.Soft.VirtualMachineManager.ConnectInternal(Socket dbg_sock, Socket con_sock, IPEndPoint dbg_ep, IPEndPoint con_ep)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at Mono.Debugger.Soft.VirtualMachineManager.ConnectCallback.EndInvoke(IAsyncResult result)
   at Mono.Debugger.Soft.VirtualMachineManager.EndConnect(IAsyncResult asyncResult)
   at Mono.Debugging.Soft.SoftDebuggerSession.<>c__DisplayClass9.<StartConnecting>b__8(IAsyncResult ar)
   --- End of inner exception stack trace ---
Mono.IOS.VisualStudio.MonoTouchPackage Error: 0 : MonoToolsSession.OnDebuggerException ()
Mono.Debugging.Soft.ConnectionException: Could not connect to the debugger. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.1.92:55200

Server stack trace: 
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at Mono.Debugger.Soft.VirtualMachineManager.ConnectInternal(Socket dbg_sock, Socket con_sock, IPEndPoint dbg_ep, IPEndPoint con_ep)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at Mono.Debugger.Soft.VirtualMachineManager.ConnectCallback.EndInvoke(IAsyncResult result)
   at Mono.Debugger.Soft.VirtualMachineManager.EndConnect(IAsyncResult asyncResult)
   at Mono.Debugging.Soft.SoftDebuggerSession.<>c__DisplayClass9.<StartConnecting>b__8(IAsyncResult ar)
   --- End of inner exception stack trace ---

Expected Results:
I would expect the Visual Studio 2013 debugger to stay hooked up to the iOS Simulator


How often does this happen? 
50% of the time.

Additional Information:

=== Xamarin Studio ===

Version 4.2.3 (build 60)
Installation UUID: a4cf19c2-e62f-437b-9e9c-ea00574be1a4
Runtime:
	Microsoft .NET 4.0.30319.34011
	GTK+ 2.24.22 theme: MS-Windows
	GTK# (2.12.0.0)

=== Xamarin.Android ===

Not Installed

=== Build Information ===

Release ID: 402030060
30c4afc300c2a39ec5300851357ce02e49dd217e
Build date: 2014-03-05 16:53:54Z
Xamarin addins: f8a9589b57c2bfab2ccd73c880e7ad81e3ecf044

=== Operating System ===

Windows 6.2.9200.0 (64-bit)

Xamarin.iOS version 1.10.47 (3d6a125d)
Comment 1 Enzo Heredia 2015-07-02 16:25:38 UTC
not reproducible 4.0.0.332