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.
Created attachment 14211 [details]
Screenshot of the unsolvable warning
Unsolvable warning in the "Xamarin" section of the "Output" window: "There is a mismatch between the installed Xamarin.iOS ... and the local Xamarin.iOS"
> There is a mismatch between the installed Xamarin.iOS (version 184.108.40.206) on
> the Mac Mac Build Host (192.168.1.56) and the local Xamarin.iOS 220.127.116.11.
> 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.
This warning is unsolvable and problematic for essentially all of the same reasons as the old, closely related Bug 23270. (Bug 23270 was aimed at removing this same warning from the "Error List" window. This new bug is about removing it from the "Xamarin" section of the "Output" window.)
(a) This warning is ignorable: these are the correct intended versions to use together.
(b) There is no such release as 18.104.22.168 for Mac or 22.214.171.124 for Windows, so it is not possible to eliminate this mismatch.
## Regression status: regression in Xamarin 4.0
BAD: XamarinVS 126.96.36.199 (944b6bd) + Xamarin.iOS 188.8.131.52 (97af501)
GOOD: XamarinVS 3.11.1594.0 (a06d6d5) + Xamarin.iOS 184.108.40.206 (1f068b4)
## Steps to reproduce
1. Open a Xamarin.iOS project in Visual Studio.
2. Connect to the build host.
3. Open the "View -> Output" window and select "Xamarin" from the "Show output from" drop-down menu at the top of that window.
The "Xamarin" section of the "Output" window shows the "mismatch" warning.
(See also the attached screenshot.)
## Expected results
With XamarinVS 3.11 + Xamarin.iOS 9.1, the "mismatch" warning did _not_ appear in the "Xamarin Log" section of the "Output" window.
(Note that the "mismatch" warning _did_ appear in the `devenv*.log` file in XVS 3.11, but that was less of a problem because users didn't look at those log files as often as the output in the IDE. The output messages that appear directly in the IDE are under closer scrutiny.)
## Possible improvements
Simply removing this warning from the "Xamarin" section of the "Output" window (and keeping it in the `Ide*.log` file) would restore XamarinVS 3.11 behavior, so that would be sufficient to eliminate the regression.
It might also be acceptable to remove the warning message entirely (from both the Output window and the `Ide*.log` file). Since this warning is very often a "false positive," I'm not sure we'd lose much by removing it. Perhaps another similar warning with a lower false positive rate could be added in some future release (tracked as a separate enhancement request).
Fixed in version 220.127.116.119 (master)
Author: Jose Gallardo
Commit: 0a76599efd8796001cd9cc006a732ae933896766 (xamarin/XamarinVS)
I have checked this issue with Xamarin.VisualStudio_18.104.22.168 and XI 22.214.171.124 and able to reproduce the reported behavior.
I have checked this issue with Xamarin.VisualStudio_126.96.36.199 i.e available in trello card and C6 monotouch-188.8.131.52_d3eb416230bbba5d3da04404006db475342d5d90. Now this issue is working fine.
*** Bug 37304 has been marked as a duplicate of this bug. ***
Fixed in version 184.108.40.206 (cycle6)
Commit: 0f9bd000f572092fc5afedc06cd9735eb6466614 (xamarin/XamarinVS)
I have checked this issue with Latest build of C6SR1 i.e
Xamarin.VisualStudio_220.127.116.11_21aad6212b81987a20109cdab39efe33b6743a2d and monotouch-18.104.22.168_122b860c6c20187619a2d762017e529a764bb854 and now this issue is working fine.
Fixed in version 22.214.171.124 (cycle6)
Commit: 7c5631694229b11320211fad4fdbe5420668a0d0 (xamarin/XamarinVS)