Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
On 3/23 everything was working with XS Stable, VS Mac Preview 5 and Xamarin VS 2017 Stable. I went to a user group that night to demo VS 2017 and VS Mac during which I had change networks. In fact ended up using a hotspot to get the Mac and PC to speak to each other. Every since then, the Mac Agent not only refuses to connect, but won't even see the hostname of my Mac on the network. I've removed VS Mac, cleared the caches, set UseDNS to No in sshd_config on the Mac and confirmed that I can SSH into the Mac with both hostname and IP address. I've also checked with netstat on the Mac that SSH is indeed establishing a connection between the two. Also, the system log on the Mac shows that sshd exits abnormally with code 255 every time I try to connect with the Mac Agent. I'm filing a bug because I have seen no one else come up with this issue. It may be an issue on the Mac as opposed to the Mac Agent. Again I'm not sure.
I see that you've already done a good deal of troubleshooting yourself. Could you please share your Xamarin logs with us (Help>Xamarin>Zip Logs) so that we can check if anything is malfunctioning there?
I looked at that a few days ago and didn't seen any error messages. Plus when I tried it again just now, the zip file is empty.
So I just installed the VS2017 update that came out yesterday. No changes made to the Mac. And now XMA connects just fine. I have no idea why which is kind of scary but for now I'm going to mark this as resolved and not reproducible because there is no longer an issue to fix.