Bug 36797 - [XVS 4.0] Unsolvable warning in the "Xamarin" section of the "Output" window: "There is a mismatch between the installed Xamarin.iOS ... and the local Xamarin.iOS"
Summary: [XVS 4.0] Unsolvable warning in the "Xamarin" section of the "Output" window:...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: 4.0.2 (C6SR2)
Assignee: Bugzilla
: 37304 ()
Depends on:
Reported: 2015-12-09 23:35 UTC by Brendan Zagaeski (Xamarin Team, assistant)
Modified: 2016-02-26 22:11 UTC (History)
6 users (show)

Tags: BZRC6S1_C5SR5S1 , _XVS1215
Is this bug a regression?: ---
Last known good build:

Screenshot of the unsolvable warning (69.62 KB, image/png)
2015-12-09 23:35 UTC, Brendan Zagaeski (Xamarin Team, assistant)

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Brendan Zagaeski (Xamarin Team, assistant) 2015-12-09 23:35:58 UTC
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 on
> the Mac Mac Build Host ( and the local Xamarin.iOS
> 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.)

In short:

(a) This warning is ignorable: these are the correct intended versions to use together.

(b) There is no such release as for Mac or for Windows, so it is not possible to eliminate this mismatch.

## Regression status: regression in Xamarin 4.0

BAD:  XamarinVS    (944b6bd) + Xamarin.iOS (97af501)
GOOD: XamarinVS 3.11.1594.0 (a06d6d5) + Xamarin.iOS (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.

## Results

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).
Comment 2 xamarin-release-manager 2015-12-15 12:21:01 UTC
Fixed in version (master)

Author: Jose Gallardo
Commit: 0a76599efd8796001cd9cc006a732ae933896766 (xamarin/XamarinVS)
Comment 4 Atin 2015-12-16 13:47:48 UTC
Reproduce Status:
I have checked this issue with Xamarin.VisualStudio_4.0.1.39 and XI and able to reproduce the reported behavior.

Screencast: http://www.screencast.com/t/LgY0jzChgj

Verified Status:
I have checked this issue with Xamarin.VisualStudio_4.0.1.61 i.e available in trello card and C6 monotouch- Now this issue is working fine.

Screencast: http://www.screencast.com/t/gQ5XvvdKAY
Comment 5 Brendan Zagaeski (Xamarin Team, assistant) 2016-01-02 20:51:01 UTC
*** Bug 37304 has been marked as a duplicate of this bug. ***
Comment 7 xamarin-release-manager 2016-01-05 21:59:04 UTC
Fixed in version (cycle6)

Author: jmt
Commit: 0f9bd000f572092fc5afedc06cd9735eb6466614 (xamarin/XamarinVS)
Comment 8 Atin 2016-01-07 10:53:26 UTC
I have checked this issue with Latest build of C6SR1 i.e 
Xamarin.VisualStudio_4.0.1.69_21aad6212b81987a20109cdab39efe33b6743a2d and monotouch- and now this issue is working fine.

Screencast: http://www.screencast.com/t/PZfXY3boB3
Comment 9 xamarin-release-manager 2016-02-26 22:11:21 UTC
Fixed in version (cycle6)

Author: jmt
Commit: 7c5631694229b11320211fad4fdbe5420668a0d0 (xamarin/XamarinVS)