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.
When establishing a connection to a mac from visual studio, the following SSH commands are issued:
tail -f /tmp/com.xamarin....broker/output.log & sleep 5; kill $!'
tail -f /tmp/com.xamarin....build/output.log & sleep 10; kill $!'
Those two commands account for 15 seconds during the initial connection to a Mac, either from Visual Studio or from MSBuild.
This is particularly visible because the connection is closed every time the current Windows session is locked. This also breaks the iOS simulator on windows, btw.
My guess is that being a bit more proactive in getting out of this tail call would make for a dramatically improved experience throughout a developer's day (particularly for an enterprise dev which auto-locks its machine).
Finally, on My mac, the expected tail output is here after a few milliseconds.
This is still present in C8.
This is a big time waster... also considering the fact that even only building a Xamarin.Android project in a solution that contains a Xamarin.iOS app stall the build, even if it's not supposed to be there.
Why is the mac involved in building a Xamarin.Android app on Windows ?
Thanks for reporting the issue and for providing feedback.
The tail command mechanism to verify the Broker and Agents initialization has been removed since we considered it non performant.
You should see the improvements from C9 builds, so the connection mechanism should be faster than before, given that it doesn't waste more time than the necessary.
Please let us know how you do see the connection mechanism now and if you have any other problem.
By now, I mark the issue as Resolved.
I'm using VS2017, using the alpha builds, and it's still taking quit a bit of time to connect, and I'd say about the same time.
I'm running Xamarin.iOS 10.4.0.33 (What's coming as latest from the VS2017RC installer). Is this high enough of a version ?