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.
A couple of days ago, our team is facing this error.
Some people are able to build the solution, some are not.
From now on we all turned of auto-updates, but how can we fix following issue ? (we are on stable update channels with latest version on both mac and windows)
Xamarin.VisualStudio.IOS.MacServer Warning: 0 : [2016-02-26 13:34:40.6816] There is a mismatch between the installed Xamarin.iOS (version 22.214.171.124) on the Mac MAL016.local (10.211.55.2) and the local Xamarin.iOS 126.96.36.199. While this may not be an issue, it might cause unexpected behaviors. When applying updates, make sure to keep both the Mac and Windows in sync.
Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2016-02-26 13:34:43.5176] Agent Designer 188.8.131.52 is running
Xamarin.Messaging.VisualStudio.MessagingService Information: 0 : [2016-02-26 13:34:43.6694] MacServer State transition from AgentsStartingState to ConnectedState on MAL016.local (10.211.55.2)
Xamarin.VisualStudio.IOS.LogHandler Information: 0 : [2016-02-26 13:34:43.8185] Connected to the Mac MAL016.local (10.211.55.2) with Full support.
Xamarin.VisualStudio.IOS.MonoTouchProjectProperties Error: 0 : [2016-02-26 13:34:46.1554] There was an error while trying to evaluate the consistency between local build and conencted Mac build.
Small bump, since this is blocking our development.
The "mismatch" warning in the log file is unfortunately usually a "false positive" and can be ignored. I have now filed Bug 39708 to recommend that this warning be removed from the log files.
The 2 versions from the log excerpt in Comment 0 (184.108.40.206 and 220.127.116.11) are indeed _compatible_.
None of the other messages in the log excerpt look problematic either. (The "error while trying to evaluate consistency" is also ignorable and has been improved in the latest Cycle 7 Preview Alpha builds.) I will accordingly mark this bug as a duplicate of Bug 39708 for now. If any of your team is still hitting problems when building, please do file a new bug (to give a nice clean starting point for any further investigation). Be sure to attach the verbose build output  from the failing build on the new bug. Thanks!
 See "Verbose Build Output" on:
*** This bug has been marked as a duplicate of bug 39708 ***