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.
Xamarin 3.6.245 emits a new warning in Visual Studio whenever it is paired to the Mac build host:
> There is a minor mismatch between the installed Xamarin.iOS (version
> 126.96.36.199) on the Mac Build Host 192.168.1.111 and the local
> Xamarin.iOS 188.8.131.52. When applying updates, make sure to keep both
> the Mac and Windows in sync.
There is _no_ way to stop this warning message because it's not possible to change the "local" Xamarin.iOS version. Although the idea of the warning is nice, I'd vote that Xamarin should not emit warnings that can't be stopped. This warning is already proving to be a bit of a confusing distraction for users .
 For example, the first post here:
Regression status: new feature in XVS 3.6.
## Steps to reproduce
1. Open a Xamarin.iOS project in Visual Studio.
2. Pair to the build host (if not already paired).
3. Look in "View -> Error List -> Warnings".
Synchronizing the SDK via "Tools -> Options -> Xamarin -> iOS Settings -> SDK Synchronization -> Check Now" has no effect on the warning.
Here's another forum post where it caused unneeded concern:
Another forum thread:
I halve checked this issue and with XVS 3.7.165 + X.iOS 184.108.40.206. Now we are not getting this warning message in Windows VS by following steps mention in bug description.
Hence closing this issue.