Bug 16068 - Unable to debug iOS applications on device after upgrading to latest alpha channel
Summary: Unable to debug iOS applications on device after upgrading to latest alpha ch...
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 1.8.x
Hardware: Macintosh Windows
: --- normal
Target Milestone: ---
Assignee: Dominique Louis
URL:
Depends on:
Blocks:
 
Reported: 2013-11-08 18:56 UTC by Paul Batum
Modified: 2017-01-04 18:10 UTC (History)
9 users (show)

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


Attachments
diagnostic build output (115.57 KB, text/plain)
2013-11-08 18:56 UTC, Paul Batum
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 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:
VERIFIED FIXED

Description Paul Batum 2013-11-08 18:56:43 UTC
Created attachment 5375 [details]
diagnostic build output

Since upgrading to the latest version of the alpha channel I get the following in my output when I build:

1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(143,3): warning : Could not load file or assembly 'Mono.Cecil.Mdb, Version=0.9.5.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' or one of its dependencies. The system cannot find the file specified.
1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(143,3): warning :    at Pdb2Mdb.Converter.Convert(String filename)
1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.MonoTouch.Common.targets(143,3): warning :    at Xamarin.MonoTouch.Build.Tasks.ConvertDebuggingFiles.Execute()


Version info:
Xamarin.Android   4.10.01057 (62077ce0)
Visual Studio plugin to enable development for Xamarin.Android.

Xamarin.iOS   1.8.314 (ceaf039e)
Visual Studio extension to enable development for Xamarin.iOS
Comment 1 Paul Batum 2013-11-08 19:06:33 UTC
On further investigation I have discovered that I am now unable to debug on my device and I assume it is related to the above error.

Here is the output from the build server:
Launching /private/var/mobile/Applications/CD250CC4-D6EF-4D4F-840D-DF7C4EC5745E/HelloiOS_App8.app -debugtrack -monodevelop-port 10000 -connection-mode usb
[08-Nov-2013 16:00:03] Unable to start the debugger, bailing out.
[08-Nov-2013 16:00:03] WaitForAppConnected Waited!
[08-Nov-2013 16:00:03] Exception while handling the VisualStudio debug connection
[08-Nov-2013 16:00:03] Exception while handling the VisualStudio logging connection
[08-Nov-2013 16:00:03] Command [DebugApplication: CommmandUrl=DebugApplication] finished (30)
Mono.Android.VisualStudio.MonoAndroidPackage 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 10.82.136.192:56325

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 10.82.136.192:56325

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 ---
Comment 2 Paul Batum 2013-11-08 20:57:16 UTC
It appears this bug, like many of the VS integration bugs, is temperamental. Although I did restart VS and the build server many times and the error persisted, after trying again an hour later it appears to work now.
Comment 4 Paul Batum 2013-11-13 17:27:39 UTC
I am no longer seeing this error after a reinstall.
Comment 5 Marek Habersack 2013-11-13 17:34:56 UTC
Great! Closing the bug based on comment #4
Comment 6 narayanp 2014-03-27 07:13:10 UTC
As per comment#4 and Comment#5 changing the status to Verified.
Comment 7 Paul Batum 2017-01-04 18:10:23 UTC
Comment on attachment 5375 [details]
diagnostic build output

<<contents removed>>