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.
# Steps to reproduce
Click the Xamarin Mac Agent in the toolbar. Prior to this update, it used to connect automatically after I connected one time.
It sees the mac, and after authentication just shows the spinner.
After some time it shows the connection
At times, it loses the connection. Never used to happen.
# Expected behavior
Connection is persistent
# Actual behavior
# Supplemental info (logs, images, videos)
# Test environment (full version information)
Could you please provide some additional information to help us diagnose this issue?
- First and most important, could you provide logs when this behavior occurs? You can go to "Help > Xamarin > Zip Logs..." and then attach the file to this bug.
- When you see the spinner, it may just be starting the agents on the Mac. Could you please check the Xamarin Output (from the Output window). It should say that it is starting Agents. For example:
>Starting Agent Build 220.127.116.110...
>Agent Build 18.104.22.1680 is running
- Also, could you please provide the Xamarin.iOS and desktop Mono versions on the Mac? This can be easily retrieved from the About Xamarin Studio page on Mac.
It happened several times yesterday, but I haven't been able to reproduce the issue today. I'll close the issue for now but will reopen and attach the information if I experience the issue at a later time.