locked
Mac Agent Not Working - Can't Connect RRS feed

  • Question

  • User134801 posted

    I updated everything to 4.0 today. I can see my Macbook using the Mac Agent - but when entering my credentials, the following error is given:

    Couldn't connect to [Mac Name].local. Please try again

    I have followed every step of the troubleshooting guide: https://developer.xamarin.com/guides/ios/getting_started/installation/windows/xamarin-mac-agent/xma-troubleshooting/

    Here is what I know:

    • I am using the correct username, verified with whoami
    • I am using the correct password
    • Mac Agent is using the correct IP address for my macbook
    • I have updated every component, on each machine, to the latest release - they're all on the Stable channel
    • Port 22 is open, as ensured by a custom rule in inbound/outbound for Windows Firewall
    • I can ping my macbook
    • I can ssh to my macbook, using port 22, using Putty

    Odd things:

    • Library/Caches/Xamarin/ does not exist
    Wednesday, November 18, 2015 4:40 AM

All replies

  • User174437 posted

    Same problem here... have you managed to figure it out?

    Wednesday, November 18, 2015 4:38 PM
  • User151404 posted

    After updating both my Windows and Mac machines, I was able to connect with the Mac Agent a few times. Then suddenly it wouldn't work anymore. I rebooted both machines and now I am stuck trying to select a Mac to use as an agent. The choose agent dialog shows a waiting icon and a disabled "Connect" button despite a right-click on my agent computer indicating that I am connected. Any ideas?

    Wednesday, November 18, 2015 6:59 PM
  • User174437 posted

    What I did to fix it was choose to manually add a Mac, and entered the Mac’s IP address. It was able to connect to it immediately and it seems to be functioning as expected.

    Wednesday, November 18, 2015 7:40 PM
  • User151404 posted

    I'll have to try that next. After rebooting (again), I chose "disconnect" and then reconnected. That appears to have solved it. Unfortunately now, every time I start Visual Studio I get the dreaded "Microsoft Visual Studio is Busy" pop-up notification.

    Wednesday, November 18, 2015 8:29 PM
  • User134801 posted

    @SheppePharis said: What I did to fix it was choose to manually add a Mac, and entered the Mac’s IP address. It was able to connect to it immediately and it seems to be functioning as expected.

    I attempted that - it resulted in an identical error. What's curious is that I'm able to establish a ssh connection with my mac by other means.

    I've started a thread on bugzilla: https://bugzilla.xamarin.com/show_bug.cgi?id=35971

    Wednesday, November 18, 2015 8:42 PM
  • User127236 posted

    @WednesdayWolf I have the same problem, I can connect through ssh but the agent never connected :neutral:

    Wednesday, November 18, 2015 9:25 PM
  • User174437 posted

    @WednesdayWolf I was also able to SSH over to my Mac from my Windows Xamarin box.

    A ticket I was referred to by Xamarin support is https://bugzilla.xamarin.com/showbug.cgi?id=34932. It didn't apply to my problem, but perhaps it does to yours (the situation in the ticket being the Mac is not connected to the internet). The workaround is to add the following line on the Mac to /etc/sshdconfig:

    UseDNS no

    Wednesday, November 18, 2015 9:32 PM
  • User134801 posted

    @SheppePharis Curious! No doubt useful to others. Doesn't apply to this situation, unfortunately - both machines are connected to the internet.

    Wednesday, November 18, 2015 9:41 PM
  • User127236 posted

    @WednesdayWolf I just get the agent to connect to my Mac. You need to activate the firewall on your Mac and allow the connection. It makes no sense but this has worked for me.

    Thursday, November 19, 2015 3:31 PM
  • User101855 posted

    @JeffGonzales I had the the same problem - Visual Studio is busy. I opened the project in Visual Studio 2013 and then reopen in Visual Studio 2015. It's funny, but it worked for me.

    Thursday, November 19, 2015 5:41 PM
  • User151404 posted

    That worked for me a couple of times, but then I started to get the problem back. If I revert to my original project in SVN it starts to work again. I wonder if Xamarin is corrupting some project files...

    Thursday, November 19, 2015 5:43 PM
  • User134801 posted

    @ciani.afonso Just tried that out - the mac was able to recognise that a ssh connection was attempting to be established. It brought up the mono-sgen prompt. I allowed the connection, and the same error message occurred in Visual Studio. "Couldn't Connect. Please try again."

    Thursday, November 19, 2015 5:56 PM
  • User127236 posted

    @WednesdayWolf Yes, I allowed that connection to mono-sgen, and it worked.

    What version of OS are you using? I'm using version El Capitan, in Yosemite version I did not get it to work.

    Friday, November 20, 2015 7:26 AM
  • User31231 posted

    All,

    For those having issues connecting with the Mac Host Agent, please try the following:

    You need to ensure that both IDEs (Xamarin Studio on the Mac, and Visual Studio on windows) are on the same updater channel, as mentioned here and you can also use the Connectivity Troubleshooting guide to double check everything else is set up properly.

    Friday, November 20, 2015 2:27 PM
  • User134801 posted

    @ciani.afonso Trying to connect to a 10.11 (El Capitan) machine.

    @KMullins They're both on the same channel, and as I said in my opening post I've followed every step of that guide.

    Friday, November 20, 2015 8:47 PM
  • User171859 posted

    Hi guys! I'm facing the same problem. Update channels are the same, both updated to latest version, tried enabling firewall on Mac, allowed a connection for mono-sgen, tried to connect manually with IP address, but nothing helped. Both computers are connected to same router with Internet connection, I can connect to my Mac via SSH with Putty, remote login is enabled for my user.

    Saturday, November 21, 2015 9:11 PM
  • User32133 posted

    I'm having the exact same issue, can't connect to my mac. Worked fine with build server. SSH connection works with putty, so it's not a configuration problem.

    Sunday, November 22, 2015 2:55 AM
  • User175281 posted

    Same here.

    I've found this messages in the VS Log: Xamarin.Messaging.VisualStudio.MessagingService+UploadFileLogger Information: 0 : [2015-11-22 13:18:00.1266] Uploaded Broker 4.0.0.1689 100% Xamarin.Messaging.Client.Ssh.XmaCommands Warning: 0 : [2015-11-22 13:18:01.0437] Checksum failed for '/Volumes/Macintosh HD/Users/markus/Library/Caches/Xamarin/XMA/Broker/4.0.0.1689' Xamarin.Messaging.VisualStudio.MessagingService Error: 0 : [2015-11-22 13:18:01.0517] Unable to install the Broker

    Sunday, November 22, 2015 1:18 PM
  • User102481 posted

    Same problem. Mac Agent worked for a couple of days and now I cannot connect. Tried most of what was suggested here to no avail on El Capitan / Win 10 / VS 2015 both Xamarin's on latest stable. Worked fine on build host, can get ssh key, sometimes the broker installs but I never get a full connection. Logs indicate cannot start broken host disconnected as mentioned above.

    Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2015-11-24 15:09:11.1684] MacServer State transition from AgentsStartingState to LimitedState on Publishing-Mac.local (10.61.4.92) Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Information: 0 : [2015-11-24 15:09:11.2580] Connected to the Mac Publishing-Mac.local (10.61.4.92) with Limited support. Xamarin.Messaging.Client.MessagingClient Error: 0 : [2015-11-24 15:09:18.9032] An error occured on client vs7512Clint while executing a post for topic xma/ping/Broker4001689 System.TimeoutException: The operation has timed out. at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Xamarin.Messaging.Client.MessagingClient.d2`2.MoveNext() Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2015-11-24 15:09:19.0348] MacServer State transition from LimitedState to DisconnectedState on Publishing-Mac.local (10.61.4.92) Xamarin.VisualStudio.IOS.Messaging.State.ServerStateContext Information: 0 : [2015-11-24 15:09:19.1219] The underlying client has been closed Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2015-11-24 15:09:19.2089] Disconnected from Mac Publishing-Mac.local (10.61.4.92) Xamarin.VisualStudio.IOS.MacServer Error: 0 : [2015-11-24 15:09:21.3258] An error occured starting the IDB 4.0.0.1689 agent: Client not connected.

    Tuesday, November 24, 2015 10:08 PM
  • User117159 posted

    Im having the same problem. I can connect through SSH but in Visual Studio it says it can't connect to mac host.

    Wednesday, November 25, 2015 12:27 PM
  • User102481 posted

    Turns out my issue was related to timeouts caused by internal network issues.

    Wednesday, November 25, 2015 2:19 PM
  • User171859 posted

    @ClintonLandry said: Turns out my issue was related to timeouts caused by internal network issues.

    Did you try to connect to Mac via SSH directly? Because I can connect directly without any issues, but Xamarin keeps giving me "can't connect" error

    Wednesday, November 25, 2015 3:24 PM
  • User102481 posted

    @AndrewNik have you read the logs (Help > Xamarin > Logs) to get a better understanding of why? It clearly told me my session was timing out while uploading the IDB agent to the mac. A speed test or two later made it clear what a possible cause was for me and after that was resolved it works perfectly fine on latest stable, Win10/VS15 to El Capitan.

    Wednesday, November 25, 2015 3:32 PM
  • User171859 posted

    @ClintonLandry I found such info there, and that looks really strange

    Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2015-11-25 17:20:23.0305] Starting Broker 4.0.0.1689 in port 51316... Xamarin.Messaging.Client.Ssh.SshCommandRunner Warning: 0 : [2015-11-25 17:20:23.2113] Failed to execute 'ls /usr/bin/mono': ExitStatus=1 Xamarin.Messaging.Client.Ssh.SshCommandRunner Warning: 0 : [2015-11-25 17:20:23.3113] /Users/andreynikolin/.bashrc: line 1: dnvm.sh: No such file or directory ls: /usr/bin/mono: No such file or directory

    Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Error: 0 : [2015-11-25 17:20:23.5331] Couldn't connect to MacBook-Pro-Andrey.local. Please try again. Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Information: 0 : [2015-11-25 17:20:23.6642] MacServer State transition from SshConnectingState to DisconnectedState on MacBook-Pro-Andrey.local (192.168.0.3) Xamarin Information: 0 : [2015-11-25 17:20:23.8128] Disconnected from Mac MacBook-Pro-Andrey.local (192.168.0.3) I've checked, such directory doesn't exist on my Macbook and I'm curious where I have to get it

    Wednesday, November 25, 2015 3:37 PM
  • User102481 posted

    @AndrewNik

    I was getting those errors as well but it was just noise resulting from my PC not getting everything it needed onto the MAC before a disconnect happened.

    Along with my office wifi not being under construction anymore I did follow suggestions above including turning the MACs firewall on and allowing mono-sgen. Followed all of the steps in the Connectivity Troubleshooting link above as well.

    Wednesday, November 25, 2015 3:50 PM
  • User171859 posted

    @ClintonLandry I'm working with this set-up at home, there are only 2 computers on the network, so I don't think the problem can be in connection between them. Firewall is enabled as well(allowed connection), and I've already tried all steps from troubleshoot guide. Just tried manually reinstalling Mono, but that didn't help.

    Wednesday, November 25, 2015 3:58 PM
  • User117159 posted

    I solved my problem by changing to Alpha channel. This was the same bug that was happening to me: https://bugzilla.xamarin.com/show_bug.cgi?id=35859 My Windows username has a "~" and it was raising an exception. Hope this can help someone

    Wednesday, November 25, 2015 5:02 PM
  • User21647 posted

    Mine had been behaving for days (I upgraded to v4 last Friday) until I started fiddling with the internet connectivity for the ios simulator by turning my wifi on and off yesterday afternoon. It was running through a wifi hotspot tether thru my mobile phone.

    After suspending/resuming my macbook (at home, on a different wifi network), VS refused to connect to the mac agent. I tried rebooting, restarting the windows VM in paralyse... I mean Parallels... no dice. The IP address of the mac host as far as my parallels instance was concerned, hadn't changed, but the internal IP address of the mac itself had, because it had connected to different wifi router, different network (192.x as opposed to 10.x).

    For a while the indicator on VS looked like it had a connection to the mac agent, but I had no ios devices listed in the dropdown for the simulator. I couldn't disconnect it (there's no button) and I couldn't refresh it (there's no button). After several restarts of VS, I was finally prompted with the mac agent connection dialog. It said it could see the mac agent on mac-host-name.local, but refused to connect to it, exactly as described ad nauseum in this thread.

    I noticed it also took frikkin age to "get the ssh fingerprint" (where normally this takes less than a second).

    And it kept telling me my login was incorrect.

    I was still able to ssh and log in to the mac host at the IP address it had for the agent (also via putty), no problem. Firewalls, blah, exactly the same as everyone else here.

    Over an hour later of banging my head on this, I ended up adding the 'UseDns=No" flag as mentioned above, and killing and restarting sshd on the mac. That didn't seem to solve the problem, but after restarting VS for the squillionth time, and getting the mac agent connection dialog back, I added a new mac, using the IP address it's always used (instead of mac-host-name.local). It took less than a second to get the ssh fingerprint, and logged me in immediately with the same credentials it's always asked for.

    At that point I was so damn glad it was working again that I let it be, and carried on. Of course I had to work for over an hour longer than I had planned to make up for the time I'd lost, which meant I only got to bed at 1am.

    Not cool.

    But when I got back on the train this morning (after suspending the macbook last night and resuming everything this morning), it prompted me to log in again. I got a sinking feeling, coupled with not a small amount of cold rage... but on a hunch, I told it to connect to the mac-host-name.local (instead of the IP address) and it worked. Straight in, no complaints, didn't even ask me for my login.

    My gut tells me that it's all got to do with the wifi network connectivity coming and going. Perhaps IP addresses of the host machine changing as they come and go. Maybe it confuses the ssh daemon or breaks the agent, something like that.

    This reminds me a lot of the same issues I used to get with the previous mac build host, during my daily commutes, where VS would not quite randomly lose the connection to the build host when the 3G/wifi hotspot tether through my phone lost the internet connectivity because I was going through a 3G/4G coverage dead spot. I'd lose internet connectivity, and then within a few seconds I'd get that error about "another instance of visual studio is using the build host" error (when there was only one instance running).

    I noticed at one point during the trip home yesterday (when going through one of those dead spots) that VS had apparently still got a the connection to the mac agent, but all the simulator devices disappeared from the dropdown. Restarting VS fixed the problem tho.

    Maybe this helps someone as well. Maybe it adds a couple more clues to why this is happening.

    Rage and despair aside, I think this mac agent is SO much better than what we had before. I think that's why I got annoyed with it so quickly when it broke, because it Just Worked, and I'd already grown used to not having to disconnect/reconnect to the mac build host again and again on my trips home on the train or bus (sometimes 2-3 times in an hour).

    Wednesday, November 25, 2015 7:53 PM
  • User171859 posted

    Xamarin.Messaging.Client.Ssh.SshCommandRunner Warning: 0 : [2015-11-25 17:20:23.2113] Failed to execute 'ls /usr/bin/mono': ExitStatus=1 Finally, looks like I found out why this happened. El Capitan restricts software installation to /usr/bin, so Mono is installed to /usr/local/bin. I think Xamarin development team has to change paths where Xamarin for VS is looking for Mono. Another way to fix this is described here http://stackoverflow.com/a/33364409/1666284 I tried creating symlink in /usr/bin, but system doesn't create it even using sudo, so it looks like I'll have to disable this system protection using the info from the link above. Or wait for fix from Xamarin. Some more info - you can make mono execute in terminal with the following command export PATH=/Library/Frameworks/Mono.framework/Versions/Current/bin/:${PATH} But Xamarin for VS executes it directly with /usr/bin/mono and that causes the problem. Mentioning @KMullins check this information, please

    Thursday, November 26, 2015 11:18 AM
  • User71545 posted

    I am stuck at the same place as @AndrewNik But have no clue how to handle this issue.

    With this issue using VS for XAMARIN dev. is no option anymore.

    Will reinstalling everything on MAC or resetting MAC and starting over again help?

    Followed answer on this link: http://stackoverflow.com/a/33364409/1666284 and install Mono after csrutil disable but that does not help.

    Anyone any idea on how to fix it or any workaround or when the fix is coming?

    Thursday, November 26, 2015 5:21 PM
  • User171859 posted

    @Jsinh I haven't checked this method yet, will try later today

    Thursday, November 26, 2015 6:14 PM
  • User171859 posted

    So I've disabled csrutil, created symlink from /usr/local/bin/mono to /usr/bin, but it still doesn't want to work. Here is the log and now I can't see any clues in it

    Xamarin.VisualStudio.IOS.Messaging.State.ServerStateContext Information: 0 : [2015-11-26 22:10:40.3336] MacServer State transition from DisconnectedState to SshConnectingState on 192.168.0.3 (192.168.0.3) Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2015-11-26 22:10:42.8231] Starting Broker 4.0.0.1689 in port 57648... Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Error: 0 : [2015-11-26 22:10:43.2284] Couldn't connect to 192.168.0.3. Please try again. Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Information: 0 : [2015-11-26 22:10:43.3158] MacServer State transition from SshConnectingState to DisconnectedState on 192.168.0.3 (192.168.0.3) Xamarin.VisualStudio.IOS.Messaging.State.ServerStateContext Information: 0 : [2015-11-26 22:10:44.1991] Disconnected from Mac 192.168.0.3 (192.168.0.3)

    Thursday, November 26, 2015 8:13 PM
  • User21647 posted

    (I'm still on Yosemite, not upgraded to El C. yet; the only reason is because I know there's issues with getting Xamarin to run on it).

    However, I can confirm that the connectivity issue is directly related to the wifi networks I'm switching between. At the office (where I initially set this up), I have no problem connecting to the original mac.local address I was using when I am at the office.

    I can't connect to the second mac (same vm host, same IP) I created at home (as described in my earlier post) in the connection list (even tho it's by IP address) when I am at the office

    When I get home, it's the opposite. I can not connect to the one I was connected to earlier at the office, and can only use the second one I created when I was at home. When I try the one I would have been using earlier that morning, at the office, I get the red-tinted dialog, the long wait for the ssh fingerprint and eventually the "no connection for you! come back one year!"

    Frustrating, to say the least, but at least this solves the problem for me. Hopefully it'll help someone else too.

    My environment:

    Macbook Pro with OSX Yosemite 10.10.5. Firewall on. Parallels Desktop 10.2.2 (29105). Running VS 2013 update 4 on Windows 7 Ultimate inside a Parallels VM.

    Build Information Release ID: 510000871 Git revision: 4e9c5abb5ffdae12ba02ac49da83f8b2011dbb88 Build date: 2015-11-12 07:16:34-05 Xamarin addins: 55007ed0e56436f385d8e26394a45be563abc7e8 Build lane: monodevelop-windows-cycle6

    Thursday, November 26, 2015 8:57 PM
  • User171859 posted

    @JohnWilson.4976 So it may be possible, that if I connect both Mac and PC to my router via Ethernet everything will run smoothly? Update: Just checked, even via Ethernet connection Xamarin doesn't work with such log

    Xamarin.VisualStudio.IOS.Messaging.State.ServerStateContext Information: 0 : [2015-11-27 19:43:25.7047] MacServer State transition from DisconnectedState to SshConnectingState on 192.168.0.7 (192.168.0.7) Xamarin.VisualStudio.IOS.Messaging.State.ServerStateContext Information: 0 : [2015-11-27 19:43:28.9690] MacServer State transition from SshConnectingState to DisconnectedState on 192.168.0.7 (192.168.0.7) Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2015-11-27 19:43:29.1020] Starting Broker 4.0.0.1694 in port 57582... Xamarin.VisualStudio.IOS.Messaging.State.ServerStateContext Information: 0 : [2015-11-27 19:43:29.2295] Disconnected from Mac 192.168.0.7 (192.168.0.7) Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Error: 0 : [2015-11-27 19:43:29.3690] Couldn't connect to 192.168.0.7. Please try again.

    Friday, November 27, 2015 5:38 PM
  • User171859 posted

    Another interesting thing I found is

    Xamarin.VisualStudio.IOS.Bonjour.BonjourDiscovery Information: 0 : [2015-11-27 19:42:59.2460] Bonjour service 'MacBook Pro - Andrey' did not respond with its IP address. Which appears before I try to establish connection

    Friday, November 27, 2015 5:47 PM
  • User71545 posted

    Got it working the hard way. I had to hard reset my MAC (did not have anything imp. on it so was easy to wipe it off).

    Reinstalled El Caption. Then installed Mono 32x / 64x from Official Mono Site. Then installed XCode. Then installed my certificates and provisioning profiles. Then installed XAMARIN.

    This time I try to connect my VS instance with MAC and viola it all worked. No delays in connection. No errors. No path error logs. Worked on WiFi to WiFi - WiFi to LAN - LAN to LAN.

    This should not be a solution but it worked.

    So now the MAC and VS on PC are connected - I am having other issue trying to run app on a real device connected to the MAC.

    Shows following error or log: "The application [blahblahblah] needs to be rebuilt due to an inconsistency between the connected Mac and the local app. Please rebuild the application and try again."

    Anyone who has clue of this issue?

    Sunday, November 29, 2015 12:51 PM
  • User124455 posted

    @Jsinh I've seen that error when moving between different dev environments (mac and pc). I guess it builds them slightly differently. All I usually do is clean the solution and rebuild. Tho I think I often end up having to uninstall the app too, so it gets installed cleanly.

    Sunday, November 29, 2015 9:12 PM
  • User124455 posted

    @AndrewNik I would have thought that would mean it would work, but maybe it's less about the wifi and more about what the agent is doing with changed network addresses. I'm still ping-ponging between the two separate "identities" I created in the list for the (same) mac depending on where I am. It's still a pita but I have no choice but to live with it until the xamarin guys (or someone with more linux-fu than me) can figure out why this is still a problem.

    Sunday, November 29, 2015 9:15 PM
  • User171859 posted

    @JohnWilson I can say you are lucky, because such solution(connecting directly to IP or to network name) doesn't work for me at all. For now I have no more clues how to fix this problem. And Xamarin support stoped replying:(

    Sunday, November 29, 2015 9:18 PM
  • User124455 posted

    @AndrewNik that really sucks, man. I know I'm one of the lucky ones. And I am expecting it to break any time, and completely lock me out of my mobile development. my employer will NOT be amused when that happens.

    Sunday, November 29, 2015 9:56 PM
  • User13824 posted

    @AndrewNik, @Jsinh, the "Failed to execute 'ls /usr/bin/mono'" warning is an unfortunate false clue. That warning message is non-fatal. XamarinVS also checks /Library/Frameworks/Mono.framework/Versions/Current/bin/mono for mono. The fact that it outputs a warning about the "failed" ls command is probably uneccessarily confusing. I have now filed a bug to request improvements for that confusing logging behavior.

    The more important error message (at least in @AndrewNik's case) is:

    /Users/andreynikolin/.bashrc: line 1: dnvm.sh: No such file or directory

    This error is the root problem in his case. At the moment, XamarinVS loads the .bashrc file from the user's home directory before it executes certain commands. This can cause unexpected problems because other SSH sessions do not load the .bashrc file by default.

    The workaround for that problem isn't too tricky: move the .bashrc file to a backup location (or you can delete it entirely if you know you don't need it). As long as the .bashrc file is no longer present under "$HOME/.bashrc", that should stop the particular cause of the problem that @AndrewNik was seeing.

    Although the workaround is fairly easy, I don't think there's really any reason XamarinVS needs to load the .bashrc file, so I have now filed another bug to request that that behavior be changed.


    See also the latest Stable release announcement for information about other known issues in the latest release, including a link to the full "Xamarin 4 Bug List." (That list now includes the 2 new bugs I mentioned above.)

    Saturday, December 5, 2015 1:46 AM
  • User171859 posted

    @BrendanZagaeski Hello! In later messages I pointed that I've disabled Mac OS security system, so I no more have messages about .bashrc or /usr/bin/mono in log(I've created symlink to mono). The most current log looks like this(tried to connect for a number of times) http://pastebin.com/M38EWXX3 (decided to post on pastebin, because quotation here doesn't have a scroll-bar).

    Saturday, December 5, 2015 10:50 AM
  • User11231 posted

    I just had similar connection issues just now. I had the disconnect after 10 seconds in the logs.

    [2015-12-07 13:57:32.6929] MacServer State transition from DisconnectedState to SshConnectingState on MACDEV02.local (10.0.0.12) [2015-12-07 13:57:42.7040] Couldn't connect to MACDEV02.local. Please try again. [2015-12-07 13:57:42.8493] MacServer State transition from SshConnectingState to DisconnectedState on MACDEV02.local (10.0.0.12)

    What worked for me was adding a new mac and using the IP address. It was recognized as another machine and I was able to connect to it immediately.

    The biggest difference was in the time it took to get the fingerprint. It was instantaneous on the working connection. [2015-12-07 14:33:43.1659] MacServer State transition from SshConnectingState to SshConnectedState on 10.0.0.12 (10.0.0.12) [2015-12-07 14:33:43.3265] MacServer State transition from SshConnectedState to AgentsStartingState on 10.0.0.12 (10.0.0.12) ... [2015-12-07 14:33:46.2957] MacServer State transition from AgentsStartingState to LimitedState on 10.0.0.12 (10.0.0.12) ... [2015-12-07 14:34:01.7110] Connected to the Mac 10.0.0.12 (10.0.0.12) with Full support.

    Monday, December 7, 2015 12:45 PM
  • User13824 posted

    @AndrewNik, unfortunately due to the (slightly incorrect) way the logging in XamarinVS currently works during that particular connection step, if you stop the warning about mono, then you also lose the real error about .bashrc. If you haven't moved or deleted your .bashrc file, then that is still the problem you are seeing.

    See the bug report for additional related details.

    Monday, December 7, 2015 10:08 PM
  • User171859 posted

    @BrendanZagaeski Yay, awesome! Just renamed .bashrc and the problem is gone. Thanks a lot! Finally can start using Xamarin for VS =)

    Monday, December 7, 2015 10:16 PM
  • User171222 posted

    Thanks renaming worked! :)

    Friday, December 11, 2015 9:43 AM
  • User182291 posted

    Very very strange issue. The answer is ElCapitan. After many attempts, research, network analysis, packet analysis, firewalls behavior, I noticed that the requests from Windows to OSX not arrived. I upgraded to ElCapitan, and I was able to connect to the Mac with amazing speed.

    Friday, December 25, 2015 12:20 AM
  • User184183 posted

    @BrendanZagaeski said: @AndrewNik, @Jsinh, the "Failed to execute 'ls /usr/bin/mono'" warning is an unfortunate false clue. That warning message is non-fatal. XamarinVS also checks /Library/Frameworks/Mono.framework/Versions/Current/bin/mono for mono. The fact that it outputs a warning about the "failed" ls command is probably uneccessarily confusing. I have now filed a bug to request improvements for that confusing logging behavior.

    The more important error message (at least in @AndrewNik's case) is:

    /Users/andreynikolin/.bashrc: line 1: dnvm.sh: No such file or directory

    This error is the root problem in his case. At the moment, XamarinVS loads the .bashrc file from the user's home directory before it executes certain commands. This can cause unexpected problems because other SSH sessions do not load the .bashrc file by default.

    The workaround for that problem isn't too tricky: move the .bashrc file to a backup location (or you can delete it entirely if you know you don't need it). As long as the .bashrc file is no longer present under "$HOME/.bashrc", that should stop the particular cause of the problem that @AndrewNik was seeing.

    Although the workaround is fairly easy, I don't think there's really any reason XamarinVS needs to load the .bashrc file, so I have now filed another bug to request that that behavior be changed.


    See also the latest Stable release announcement for information about other known issues in the latest release, including a link to the full "Xamarin 4 Bug List." (That list now includes the 2 new bugs I mentioned above.)

    This worked for me. I renamed my .bash and it connected.

    Friday, January 1, 2016 2:12 AM
  • User194178 posted

    Have a look at this please, this is how I solved my problem, hope it helps you as well:

    https://forums.xamarin.com/discussion/60149/os-x-el-capitan-10-11-3-breaks-xamarin-and-build-host-in-ios

    Friday, February 19, 2016 2:46 PM
  • User21404 posted

    If anyone is still having this issue, i ran visual studio as Administrator and it now connects fine. It just gets hung up i believe

    Wednesday, March 2, 2016 5:33 PM
  • User201656 posted

    Edit: I had asked @NurhakKaya how they resolved their issue through that link but it appears I thought the link led to bugzilla. Thanks for the answer @NurhakKaya!

    Edit 2: Well. Not quite working for me actually. This is a real bummer but it happens with whatever stack. Hours spent on debugging the environment itself...

    Saturday, March 5, 2016 10:23 PM
  • User205985 posted

    I fixed this by creating a new admin user xamarin same full name and user name. I made sure full name and user name were the same with no spaces.

    Sunday, March 20, 2016 11:15 PM
  • User212148 posted

    Having same problem,i fixed by 1- click Add Mac 2- i added the real IP for Mac-Book Then click add and connect and it works

    Wednesday, April 6, 2016 1:32 PM
  • User209429 posted

    Try restarting VS, worked for me

    Friday, May 27, 2016 7:15 AM
  • User212548 posted

    Hey all,

    I run OSX on a local VM on my Windows 10 machine. This set up has worked well the past few months until this morning. Yesterday I updated Xamarin in Visual Studio 2015 and on my OSX instance. Then I continued working all day.

    This morning I could not connect to my Mac Agent. So I started troubleshooting the problem.

    1. Connected to the MacMini I have on the network fine. So, The issue is on my VM version of OSX.
    2. Can SSH to the VM
    3. Check the logs and see the problem is a hung broker on my OSX instance.
    4. Deleted the XMA Folder on OSX and forced it to regenerate.

    Issue fixed.

    Friday, June 24, 2016 5:50 PM
  • User124814 posted

    Hello... for what it's worth, I solved the issue adding my Mac's IP Address to my Windows HOSTS file (C:\Windows\System32\drivers\etc\hosts):

    192.168.91.128 MacDev01 MacDev01.local

    After that, the agent connected correctly.

    Tuesday, June 28, 2016 3:40 PM
  • User159923 posted

    @Ciani Afonso thanks for your help i do turn on firewall in my mac and connected to it.

    Wednesday, July 27, 2016 5:21 AM
  • User53187 posted

    I had the same issue. Xamarin logs had invalid character . After a lot of messing it turned out I had a custom bash login message, which was more than the single line of time and last login. Once I changed it to the default the connection worked fine. Upshot is that the routine to connect is not very tolerant of anything.

    Monday, August 8, 2016 5:46 PM
  • User200049 posted

    I hate @Xamarin whenever they don't care about this issues. Well, they have docs out there but some of them doesn't really help. You only consume a lot of hours.

    Tuesday, August 9, 2016 7:04 AM
  • User218476 posted

    I had this same issue. Checked the link that @WednesdayWolf provided (https://bugzilla.xamarin.com/show_bug.cgi?id=35971) and that helped me. I had the same symptoms described in that bug. For me, I did not have to physically connect via wired network connection, but was able to simply enter the IP directly instead of looking for the name of the machine.

    Tuesday, August 9, 2016 5:38 PM
  • User13824 posted

    Unfortunately networking does introduce several potential environmental complexities compared to a single-computer development setup, so detailed user bug reports of particular environments where the current logic does not succeed (or where the logging messages do not provide sufficient diagnostic information) are quite valuable. (Bug reports are the essential unit of information the engineering team will consume to understand how to improve the connection process in the future. Other approaches such as exploratory testing and code cleanup are on-going, but they do not provide the level of concrete feedback that bug reports can provide.) The subtlety of network configuration specifics also means that a precise methodical approach is important when attempting to diagnose issues with the connection process.

    The troubleshooting guide provides instructions about the recommended steps to take to file a new detailed user report in Bugzilla. From step 9 of the troubleshooting guide:

    If the ls command works correctly but the Visual Studio connection still fails, you can check the "Known Issues and Limitations" section about complications specific to Xamarin. If none of those match your problem, please file a new bug report and attach the logs described under "Check the Verbose Log Files".

    Do be sure to check each of the "Known Issues and Limitations" and then be sure to attach the verbose log files on the bug report as described. Thanks in advance!

    Wednesday, August 10, 2016 5:33 PM
  • User153440 posted

    @JamesLeichter said: If anyone is still having this issue, i ran visual studio as Administrator and it now connects fine. It just gets hung up i believe

    This answer solved my problem, thanks! Please add it to the "Known Issues and Limitations" section.

    Wednesday, August 10, 2016 8:15 PM
  • User248700 posted

    Thanks @BrendanZagaeski , I did do a WireShark trace (detailed Xamarin logs don't show much) but having some issue logging in to bugzilla so can't file the bug now. Not actually sure what info you can get from wireshark either since the packets are all encrypted. Anyway, what seems to work for me is as reported above - some combination of restarting VS2015, connecting using IP address, deleting & re-creating the IP address mac agent, then restarting VS. Problem is it seems I have to do that each day.

    Thursday, August 11, 2016 6:15 PM
  • User1814 posted

    I've run into this both times I've tried to use the iOS version with Vistual Studio. After going through the troubleshooter, each time it started working when I started the step of running Vistual Studio from a Developer Command Line with the log option: devenv /log

    How could this possibly make a difference? Seems like this bug is still present in 4.1.2. Can it not be reproduced?

    Monday, August 22, 2016 10:35 AM
  • User242158 posted

    @ClintonLandry Thank you! your solution helped me. I found issue from Help > Xamarin > Log.

    Thursday, August 25, 2016 10:17 PM
  • User253198 posted

    I have just solved this problem!!! It was nonsense. To connect visual studio Xamarin project and simulate that on mac when you getting could't connect to computername.local please try again later. You need to do next! 1. Follow the solution from xamarin community about mac connection after this point if everything OK, you will connect, but if no.. 2. Install XAMARIN STUDIO and Xcode on MAC. After installation start XAMARIN studio or Xcode, create your own app and run app with simulator. Just to test simulator. Then do not close simulator 3. Close app and try to connect again from Windows computer. At this point you will make synchronization and that all. Problem solved! I hope this gone be useful for somebody.

    I have successfully connected 2 computers with mac after doing this.

    Monday, September 12, 2016 11:07 AM
  • User12211 posted

    @JevgenijKononov said:

    1. Install XAMARIN STUDIO and Xcode on MAC.

    If you're following the instructions correctly, that should have already been done. It's the first actual install step in the Xamarin.iOS for Windows installation guide.

    Monday, September 12, 2016 4:45 PM
  • User262654 posted

    Have the same issue. The error is different from others:

    Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2016-10-04 11:19:14.7645] Starting Broker 4.2.0.695 in port 57880... Xamarin.Messaging.Client.Ssh.SshCommandRunner Warning: 0 : [2016-10-04 11:19:14.9746] Failed to execute 'mkdir -p "/tmp/com.xamarin.2016-10-0410-39-31.24096.broker"': ExitStatus=1 Xamarin.Messaging.Client.Ssh.SshCommandRunner Warning: 0 : [2016-10-04 11:19:14.9936] mkdir: /tmp/com.xamarin.2016-10-0410-39-31.24096.broker: Operation not permitted

    Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Error: 0 : [2016-10-04 11:19:15.0036] mkdir: /tmp/com.xamarin.2016-10-04__10-39-31.24096.broker: Operation not permitted

    Xamarin.Messaging.Client.Ssh.SshCommandException: mkdir: /tmp/com.xamarin.2016-10-04__10-39-31.24096.broker: Operation not permitted

    at Renci.SshNet.SshCommandExtensions.ThrowIfError(SshCommand command) at Xamarin.Messaging.Client.Ssh.SshCommands.d43.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.Ssh.SshCommands.d21.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.Ssh.SshCommands.d63.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.Ssh.SshCommands.d33.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.Ssh.BrokerCommands.d9.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.VisualStudio.MessagingService.d91.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 System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Xamarin.Messaging.VisualStudio.MessagingService.d__71.MoveNext() Xamarin.VisualStudio.IOS.Messaging.State.DisconnectedState Error: 0 : [2016-10-04 11:19:15.0313] Couldn't connect to Mykhailos-Mac.local. Please try again.

    So I've tried to create folder /tmp/com.xamarin.2016-10-04__10-39-31.24096.broker with no luck. Changing permission to tmp folder also did not helped.

    Tuesday, October 4, 2016 9:26 AM
  • User263681 posted

    Just simply restart your VS after taking the BETA updsate from Tool--Xamarin---Others

    Wednesday, October 12, 2016 1:06 PM
  • User223656 posted

    Delete every thing from the folder %localappdata%\Xamarin\MonoTouch.

    Wednesday, October 19, 2016 1:41 PM
  • User65186 posted

    Thanks @mubi!

    Thursday, October 27, 2016 7:54 PM
  • User264917 posted

    I had the same connectivity problem. It was the first time that I was connecting VS to a mac server and when I was prompted to choose a mac server, there was already one the list, that VS detected automatically. When I tried to use that one, he just kept trying to connect with no success. I followed what @SheppePharis did (added a new mac server manually by IP) and it all started working! The connectivity issues were gone and I was able to use the masc server to build and debug.

    Wednesday, November 16, 2016 10:52 AM
  • User46691 posted

    I FINALLY figured out my issue with Mac Agent not connecting. It was a DNS issue. I could use Putty from my PC to connect to the MAC, but when I tried to use the Mac Agent, it would time out. So, I finally tried pinging the name Visual Studio was using for my Mac and it didn't route to the proper IP. http://superuser.com/questions/958991/windows-10-cant-edit-hosts-file shows how to edit your Windows Hosts file to hard code a DNS entry. I did that, and whala, it connects!

    Wednesday, November 16, 2016 3:49 PM
  • User215636 posted

    My Error in mac /var/logs/system.log:

    Nov 28 10:40:54 CompanyMBP sshd[1382]: Accepted keyboard-interactive/pam for Company MacBookPro from 111.116.14.3 port 11142 ssh2 Nov 28 10:42:00 CompanyMBP sshd[1389]: Accepted keyboard-interactive/pam for Company MacBookPro from 111.116.14.3 port 11215 ssh2 Nov 28 10:42:00 CompanyMBP sshd[1392]: Accepted keyboard-interactive/pam for Company MacBookPro from 111.116.14.3 port 11216 ssh2 Nov 28 10:42:01 CompanyMBP sshd[1393]: Received disconnect from 111.116.14.3: 11: Connection terminated by the client. Nov 28 10:42:01 CompanyMBP sshd[1393]: Disconnected from 111.116.14.3 Nov 28 10:42:01 CompanyMBP com.apple.xpc.launchd[1] (com.openssh.sshd.9025155C-7BF0-4F73-937C-4FEB3B805206[1389]): Service exited with abnormal code: 255 Nov 28 10:42:01 CompanyMBP sshd[1397]: Received disconnect from 111.116.14.3: 11: Connection terminated by the client. Nov 28 10:42:01 CompanyMBP sshd[1397]: Disconnected from 111.116.14.3

    Message when connect to mac with vs 2012 "Couldn't connect to [Mac Name].local. Please try again" My solution Update de Xamarin Studio and Xcode in the mac at resolved my problem

    Monday, November 28, 2016 11:29 AM
  • User253904 posted

    Deleting the XMA Folder on the mac machine don't work.

    Tuesday, November 29, 2016 2:51 PM
  • User92206 posted

    Running VS as admin + using my username (and not my name/surname) solved my problem.

    Friday, December 16, 2016 12:50 AM
  • User10457 posted

    I have different error in the log:

    Xamarin.Messaging.Client.Ssh.XmaCommands Error: 0 : [2017-02-09 21:25:59.8379] An error occurred while verifying installed C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Xamarin\Xamarin\4.2.2.11\Broker.zip System.UnauthorizedAccessException: Access to the path 'C:\Users\jeff\AppData\Local\Temp\Xamarin\XMA\Broker\4.2.2.11' is denied.

    But I have resolved it by chaning the permission and owner of the Xamarin folder. How to change? Right click the folder. Choose properties, then choose 'Security Tab'. Start with changing the permission by clicking on the user name. Then, click Edit button. In order to change the owner, you need to click on the 'advanced' button. Then choose 'owner' tab.

    Hope this help.

    Besides, I have done something on my mac machine too. 1. I have turn off my firewall in Mac. 2. I have removed the # of UseDNS no from the sshdconfig file (sitting inside mac's HD \ etc \ ssh \sshdconfig 3. Created a dummy (blank) .bashrc file in Users\yourself\

    Thursday, February 9, 2017 9:52 PM
  • User303435 posted

    Finally I solved the timeout problem, that's because I install OzCode & ReSharper on my VS2015, after remove them I can connect Mac Agent, then install them back. All is fine.

    Saturday, March 11, 2017 3:13 AM
  • User110752 posted

    i am also got same problem from VS2017 Forms Preview , just update latest xamarin version from mac ,now its start working

    Saturday, March 11, 2017 5:38 AM
  • User316800 posted

    I had the same error message running OSX 10.12.5 Beta and Windows 10 in Parallels running VS2017 Community 15.1

    Looking at Xamarin Log %APPDATA%\Local\Xamarin\Logs\15.0 I had following error>>>>

    Xamarin.Messaging.Ssh.MessagingService|Information|0|Starting Broker 4.4.0.34 in port 50377... Xamarin.Messaging.Ssh.SshCommands|Error|0|Could not find a Mono installation on the Mac Xamarin.Messaging.Ssh.SshCommands|Error|0|Probed locations for Mono on the Mac: /usr/bin/mono64, /Library/Frameworks/Mono.framework/Versions/Current/bin/mono64

    I Downloaded Mono from http://www.mono-project.com/download/

    And now all works fine.

    Thursday, April 13, 2017 9:30 AM
  • User328604 posted

    I was able to fix this by:

    1. Looking at the Visual Studio logs to see the error
    2. Fiddling with my /etc/ssh/ssshd_config file on my Mac
    3. Restarting sshd on my Mac to get it working

    My Setup

    • Parallels and Windows 10
    • Mac OS Sierra
    • Visual Studio 2015
    • Xamarin, Latest on stable channel on both Mac and on Windows 10
    • Using zsh on Mac (oh-my-zsh)
    • I can connect to my Mac using ssh from the windows machine: ssh MYUSERNAME@192.168.2.21 works.

    The error in my Visual Studio log (C:\Users\MYUSERNAME\AppData\Local\Xamarin\Logs\14.0)

    Xamarin.VisualStudio.Remote.State.DisconnectedState|Error|0|Invalid credentials. Please try again. Xamarin.Messaging.Ssh.Exceptions.MessagingAuthenticationException: Could not authenticate the user MYUSERNAME with the provided credentials ---> Renci.SshNet.Common.SshAuthenticationException: No suitable authentication method found to complete authentication (publickey,password). at Renci.SshNet.ClientAuthentication.Authenticate(IConnectionInfoInternal connectionInfo, ISession session)

    I had to update my /etc/ssh/sshd_config file on my Mac to make it work

    This option was turned off: ChallengeRepsonseAuthentication no

    I turned it back on:

    ```

    Change to no disable s/key passwords

    ChallengeResponseAuthentication yes ```

    And that fixed it.

    My /etc/ssh/sshd_config file settings

    If you're interested, these are all the settings in my /etc/ssh/sshd_config without comments:

    LogLevel DEBUG3 AuthorizedKeysFile .ssh/authorized_keys PasswordAuthentication yes ChallengeResponseAuthentication yes UsePAM yes ClientAliveInterval 20 ClientAliveCountMax 5 UseDNS no AcceptEnv LANG LC_* Subsystem sftp /usr/libexec/sftp-server

    Monday, June 5, 2017 4:00 PM
  • User17785 posted

    In my case. I found the following in VS Log:

    Xamarin.Messaging.Ssh.MessagingService|Information|0|Starting connection to Mac 10.36.101.162... Xamarin.Messaging.Ssh.XmaCommands|Warning|0|Integrity check failed between deployed content and local copy. Server path: /Users/dave/Library/Caches/Xamarin/XMA/Broker/4.5.0.486, Local path: C:\Users\davimont\AppData\Local\Temp\Xamarin\XMA\Broker\Broker.4.5.0.486.md5 Xamarin.Messaging.Ssh.MessagingService|Information|0|Installing Broker 4.5.0.486... Xamarin.Messaging.Ssh.XmaCommands|Warning|0|Integrity check failed between deployed content and local copy. Server path: /Users/dave/Library/Caches/Xamarin/XMA/Broker/4.5.0.486, Local path: C:\Users\davimont\AppData\Local\Temp\Xamarin\XMA\Broker\Broker.4.5.0.486.md5 Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (160/1538 KB) 10%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (320/1538 KB) 20%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (464/1538 KB) 30%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (624/1538 KB) 40%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (784/1538 KB) 50%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (928/1538 KB) 60%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (1088/1538 KB) 70%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (1232/1538 KB) 80%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploading Broker 4.5.0.486 (1392/1538 KB) 90%... Xamarin.Messaging.Ssh.MessagingFileManager+UploadFileLogger|Information|0|Uploaded Broker 4.5.0.486 100% Xamarin.Messaging.Ssh.XmaCommands|Warning|0|Integrity check failed between deployed content and local copy. Server path: /Users/dave/Library/Caches/Xamarin/XMA/Broker/4.5.0.486, Local path: C:\Users\davimont\AppData\Local\Temp\Xamarin\XMA\Broker\Broker.4.5.0.486.md5 Xamarin.Messaging.Ssh.MessagingService|Error|0|Unable to install the Broker Xamarin.VisualStudio.Remote.State.DisconnectedState|Error|0|Couldn't connect to 10.36.101.162. Please try again

    Deleting the XAM folder in both the MAC and the PC in the Local/Temp/Xamarin folder did the work. =)

    Wednesday, June 28, 2017 5:30 PM
  • User311778 posted

    Don't forget to install XCode and Android Studio (or Visual Studio for Mac).

    Both are necessary to run on iOS.

    Wednesday, July 12, 2017 6:49 PM
  • User43921 posted

    I've actually repaired Xamarin's stuff and sent it back to them for some time. In 2014 they shipped the first versions of Visual Studio support, including project templates. At that time even their"Hello World" template was broken. I couldn't direct potential customers to their examples, since most were broken. I had to fix a set that I could demonstrate to customers. It's sad that this state of affairs continues - I just had similar problems about the build server on VS2017. The lack of quality control is allowing things like React Native to gain traction. I know many folks who have switched to it, sadly.

    Saturday, September 2, 2017 7:27 PM
  • User158279 posted

    So just to add another thing to try if you run into this issue. That I didnt see documented anywhere else. In a 64-bit version of Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 you need https://support.microsoft.com/en-us/help/2588507/error-messages-when-a-32-bit-application-has-the-largeaddressaware-opt to get the connection from VS to Mac working.

    Monday, September 11, 2017 9:58 PM
  • User328941 posted

    If you updated xcode make sure you start xcode up on the mac and accept the terms. Yes ... AGAIN

    *BecauseItsALittleBiyach

    Wednesday, October 4, 2017 10:31 PM
  • User5742 posted

    @JoeJohnston said: If you updated xcode make sure you start xcode up on the mac and accept the terms. Yes ... AGAIN

    *BecauseItsALittleBiyach

    +1 for starting up xcode again

    Tuesday, November 7, 2017 10:11 AM
  • User326903 posted

    Using the IP address worked for me. Also I had to be logged in my Mac using the same credentials as in VS.

    Tuesday, December 12, 2017 5:30 AM
  • User369487 posted

    error while connectin to mac . mac in installed on VMWare .


    Thursday, June 7, 2018 7:38 AM