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.
MacBookPro running Xamarin build host (10.10.3, latest Xamarin as of 28th April 2015)
Surface Pro 2 running VS2013 community (Windows 8.1, latest Xamarin as of 28th April 2015)
Create a new Xamarin Forms project.
After a while the MBP goes to sleep, and the connection to the iOS build host is lost. The VS error panel pops up with a warning about a lost connection and an error about another instance of VS using the build host.
This pops up every second - closing the panel or hiding it doesn't work, it still pops up. Not only is it distracting but the focus is stolen from the editor so you can't even carry on typing.
The only workaround is to wake the Mac up, double click on the error to reconnect, choose the same build host as before and let it connect - it doesn't even reconnect automatically.
Removing the iOS project from the solution makes no difference, it still wants to connect.
It should only error on building, not whilst purely coding. It also shouldn't error if the iOS projects in the solution are removed.
could you copy/paste the Help | About Microsoft Visual Studio version information?
I can't repro this with our latest stable. Timing might have been against you in this particular case. The new stable bits shipped the day after you reported the issue :(.
The new stable build is 3.11.445.
Verified as fixed in 3.11.445. It's now a warning and we no longer force-show the error list.