Bug 40079 - Unable to fully start the Xamarin Mac Agent. Designer 4.0.3.214 when trying to connect to the Mac
Summary: Unable to fully start the Xamarin Mac Agent. Designer 4.0.3.214 when trying ...
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: XMA ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-04-04 13:21 UTC by David Harris
Modified: 2016-04-13 15:51 UTC (History)
7 users (show)

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


Attachments
Visual Studio Log File (51.99 KB, text/plain)
2016-04-04 13:21 UTC, David Harris
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:
RESOLVED FIXED

Description David Harris 2016-04-04 13:21:41 UTC
Created attachment 15594 [details]
Visual Studio Log File

When connecting to my VMWare Mac (Running El Capitan 10.11) using Visual Studio 2013 Community, it gets so far, but comes up with the following error.

The Xamarin Mac Agent could not be fully started.  Agents not started: Designer 4.0.3.214. Please check the logs for details.

I have installed Xamarin and Xcode on the MAC and are logged into both.  I can open the iOS simulator okay, but when I try to open an iOS project in Visual Studio I get the following error. (The iOS Designer Mac Agent is not available)

I have attached the log from Visual Studio.

I have attempted to Uninstall and re-install Xamarin for Visual Studio but still have no joy.

Any advice would be appreciated.

Thanks
Comment 1 Alan McGovern 2016-04-04 13:32:25 UTC
It looks like an error is happening before the designer related code is initialised. Reassigning to the appropriate component.
Comment 2 David Harris 2016-04-04 15:09:30 UTC
To give some more info. 

I can see the following error in the Apple Console Logs when the Designer Agent attempts to start

com.apple.xpc.launchd:
(com.xamarin.designer.5ba2cdb8[3646]) Service exited due to signal: Killed: 9

Thanks
Comment 3 David Harris 2016-04-04 16:29:11 UTC
This is the output from Visual Studio when connecting to the Mac

Bonjour service 'Dave’s iMac' did not respond with its IP address.
Starting Broker 4.0.3.214 in port 53717...
SSH Connection established with the Mac 192.168.110.128:53717
Starting agents on Mac 192.168.110.128 (192.168.110.128)
Starting Agent IDB 4.0.3.214...
Agent IDB 4.0.3.214 is running
Installing Agent Build 4.0.3.214...
Uploading Build 4.0.3.214 (160/1574 KB) 10%...
Uploading Build 4.0.3.214 (320/1574 KB) 20%...
Uploading Build 4.0.3.214 (480/1574 KB) 30%...
Uploading Build 4.0.3.214 (640/1574 KB) 40%...
Uploading Build 4.0.3.214 (800/1574 KB) 50%...
Uploading Build 4.0.3.214 (960/1574 KB) 60%...
Uploading Build 4.0.3.214 (1104/1574 KB) 70%...
Uploading Build 4.0.3.214 (1264/1574 KB) 80%...
Uploading Build 4.0.3.214 (1424/1574 KB) 90%...
Uploaded Build 4.0.3.214 100%
Starting Agent Build 4.0.3.214...
Agent Build 4.0.3.214 is running
Installing Agent Designer 4.0.3.214...
Uploading Designer 4.0.3.214 (2800/27969 KB) 10%...
Uploading Designer 4.0.3.214 (5600/27969 KB) 20%...
Uploading Designer 4.0.3.214 (8400/27969 KB) 30%...
Uploading Designer 4.0.3.214 (11200/27969 KB) 40%...
Uploading Designer 4.0.3.214 (14000/27969 KB) 50%...
Uploading Designer 4.0.3.214 (16784/27969 KB) 60%...
Uploading Designer 4.0.3.214 (19584/27969 KB) 70%...
Uploading Designer 4.0.3.214 (22384/27969 KB) 80%...
Uploading Designer 4.0.3.214 (25184/27969 KB) 90%...
Uploaded Designer 4.0.3.214 100%
Starting Agent Designer 4.0.3.214...
An error occured starting the Designer 4.0.3.214 agent: Archive:  csproxy.zip
  inflating: csproxy                 
Xamarin.Messaging.Client.AgentConsoleRunner Information: 0 : ==== :: Xamarin :: 4.0.3.214-cycle6-c6sr3+0dd817c ====
Xamarin.Messaging.Client.AgentConsoleRunner Information: 0 : Starting Designer 4.0.3.214...
Xamarin.Messaging.Designer.DesignerAgent Information: 0 : MDAddinsHash: c510236bc65db72fa8b900951ed4680b6a5e63fa

Failed-Object reference not set to an instance of an object
Xamarin.Messaging.Client.AgentConsoleRunner Error: 0 : 

The Xamarin Mac Agent could not be fully started. Agents not started: Designer 4.0.3.214. Please check the logs for more details.
Connected to the Mac 192.168.110.128 (192.168.110.128) with Limited support.
Comment 4 David Harris 2016-04-04 16:57:01 UTC
More Log Info 


<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
<EventID>0</EventID>
<Type>3</Type>
<SubType Name="Warning">0</SubType>
<Level>4</Level>
<TimeCreated SystemTime="2016-04-04T16:14:26.8547741Z" />
<Source Name="Xamarin.VisualStudio.IOS.XamarinIOSPackage" />
<Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
<Execution ProcessName="devenv" ProcessID="13664" ThreadID="7" />
<Channel />
<Computer>OFFICE-PC</Computer>
</System>
<ApplicationData>Initializing Xamarin.VisualStudio.IOS.XamarinIOSPackage.</ApplicationData>
</E2ETraceEvent>


<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
<EventID>0</EventID>
<Type>3</Type>
<SubType Name="Error">0</SubType>
<Level>2</Level>
<TimeCreated SystemTime="2016-04-04T16:15:55.7386025Z" />
<Source Name="Xamarin.Messaging.Client.MessagingClient" />
<Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
<Execution ProcessName="devenv" ProcessID="13664" ThreadID="52" />
<Channel />
<Computer>OFFICE-PC</Computer>
</System>
<ApplicationData>An error occured on the receiver while executing a post for topic xvs/idb/4.0.3.214/set-settings and client vs13664DaveO
Xamarin.Messaging.Exceptions.MessagingRemoteException: An error occured on client IDB403214 while executing a reply for topic xvs/idb/4.0.3.214/set-settings ---> System.NullReferenceException: Object reference not set to an instance of an object
  at Xamarin.Messaging.IDB.AppleSettingsProvider.GetSupportFlags () <0x70a5000 + 0x0001f> in <filename unknown>:0 
  at Xamarin.Messaging.IDB.Handlers.SetSettingsMessageHandler+<>c__DisplayClass2_0.<ExecuteAsync>b__0 () <0x709f108 + 0x002e8> in <filename unknown>:0 
  at System.Threading.Tasks.Task`1[TResult].InnerInvoke () <0x1922bb0 + 0x00054> in <filename unknown>:0 
  at System.Threading.Tasks.Task.Execute () <0x1935780 + 0x0004d> in <filename unknown>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x188f5d0 + 0x00035> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x188cf00 + 0x000b7> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x188ce60 + 0x00087> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x188ce10 + 0x0003f> in <filename unknown>:0 
  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () <0x188d600 + 0x00024> in <filename unknown>:0 
  at Xamarin.Messaging.IDB.Handlers.SetSettingsMessageHandler+<ExecuteAsync>d__2.MoveNext () <0x709e9b8 + 0x0021b> in <filename unknown>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x188f5d0 + 0x00035> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x188cf00 + 0x000b7> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x188ce60 + 0x00087> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x188ce10 + 0x0003f> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () <0x188d180 + 0x00024> in <filename unknown>:0 
  at Xamarin.Messaging.Client.RequestHandler`2+<HandleAsync>d__5[TMessage,TResult].MoveNext () <0x709deb0 + 0x003d7> in <filename unknown>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x188f5d0 + 0x00035> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x188cf00 + 0x000b7> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x188ce60 + 0x00087> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x188ce10 + 0x0003f> in <filename unknown>:0 
  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () <0x188d600 + 0x00024> in <filename unknown>:0 
  at Xamarin.Messaging.Client.MessageHandlerManager+<>c__DisplayClass16_0`2+<<RegisterHandlerAsync>b__1>d[TMessage,TResult].MoveNext () <0x709d4e0 + 0x002bb> in <filename unknown>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x188f5d0 + 0x00035> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) <0x188cf00 + 0x000b7> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) <0x188ce60 + 0x00087> in <filename unknown>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) <0x188ce10 + 0x0003f> in <filename unknown>:0 
  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () <0x188d600 + 0x00024> in <filename unknown>:0 
  at Xamarin.Messaging.Client.MessagingClient+<ReplyAsync>d__34`2[TRequest,TResponse].MoveNext () <0x709c6d0 + 0x00383> in <filename unknown>:0 
   --- End of inner exception stack trace ---
   at Xamarin.Messaging.Client.MessagingClient.<PostAsync>d__23`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.Messaging.Client.MessagingClient.<PostAsync>d__22`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.Messaging.Client.MessagingClient.<PostAsync>d__26`2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Xamarin.VisualStudio.IOS.SettingsProvider.<RefreshSettingsAsync>d__46.MoveNext() in C:\Users\builder\data\lanes\3062\0dd817c0\source\XamarinVS\src\Core\VisualStudio.IOS\IDB\SettingsProvider.cs:line 77</ApplicationData>
</E2ETraceEvent>
Comment 5 David Harris 2016-04-04 23:21:02 UTC
I have now managed to get the agent Designer connected and running.  Hence I am setting this ticket to resolved.

I now have another issue that I will raise a new ticket for

Kind Regards

Dave
Comment 6 Alan McGovern 2016-04-05 01:44:53 UTC
It looks like there is an actual bug in the logs you've filed, so i think we should leave this open until we can address it. Perhaps it's a race condition which is why it suddenly started working, or maybe there is an issue handling Xcode which triggered the problem. I'm not familiar with that area, but the person who is will be able to look into it and see if the exception in your logs can be solved permanently.
Comment 7 rconde01 2016-04-10 22:50:56 UTC
I'm seeing this same error - David, what did you do to resolve it?

For reference:

Starting Agent Designer 4.0.3.214...
An error occured starting the Designer 4.0.3.214 agent: Xamarin.Messaging.Client.AgentConsoleRunner Information: 0 : ==== :: Xamarin :: 4.0.3.214-cycle6-c6sr3+0dd817c ====
Xamarin.Messaging.Client.AgentConsoleRunner Information: 0 : Starting Designer 4.0.3.214...
Xamarin.Messaging.Designer.DesignerAgent Information: 0 : MDAddinsHash: c510236bc65db72fa8b900951ed4680b6a5e63fa

Xamarin.Messaging.Client.AgentConsoleRunner Error: 0 : $An unexpected error occurred and the agent 'Designer 4.0.3.214' will be terminated
Failed-Object reference not set to an instance of an object
Comment 8 Vincent Sauvage 2016-04-13 15:02:55 UTC
@rconde01

I had the same error, resolved by installing the Xamarin IDE on the Mac.

I was pointed in that direction by a post from Jose Gallardo (Xamarin) on StackOverflow:

<< Xamarin for Visual Studio doesn't install some requirements on the Mac side like Xamarin.iOS, Xamarin.Mac and Mono. All of those are requirements that are installed by the Xamarin Studio installer on the Mac (from http://xamarin.com/download). You should hit that URL from the Mac itself to get the Mac download, otherwise you'll see the Windows download. >>

If this is the proper action to perform, I believe the ticket can be closed.
Comment 9 Alan McGovern 2016-04-13 15:51:51 UTC
The 'unable to fully start' message can be shown for a variety of reasons, so there are a variety of possible solutions. We'll investigate the specific error mentioned in comment 4 separately, as part of bug #40346. For now we can just close this.

Thanks!