Bug 29782 - Version mismatch in Xamarin.iOS after updating Forms to
Summary: Version mismatch in Xamarin.iOS after updating Forms to
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 1.4.3
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-05-06 04:53 UTC by John Hardman
Modified: 2016-01-04 16:55 UTC (History)
3 users (show)

Tags: iOS Xamarin version mismatch
Is this bug a regression?: ---
Last known good build:

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 or GitHub 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 John Hardman 2015-05-06 04:53:12 UTC
After updating Xamarin.Forms to, the following is reported when attempting to run the iOS project:

PrototypeiOS[595:7535] Version mismatch between the native Xamarin.iOS runtime and Xamarin.iOS.dll. Please reinstall Xamarin.iOS.

A few more details of the exception that result follow:

-		Instance	{ObjCRuntime.RuntimeException}	ObjCRuntime.RuntimeException
-		base	{System.Exception}	System.Exception
+		Data	Count = 0	System.Collections.Generic.Dictionary<object,object>
		HResult	-2146233088	int
		HelpLink	(null)	object
		InnerException	(null)	object
		Message	"Version mismatch between the native Xamarin.iOS runtime and Xamarin.iOS.dll. Please reinstall Xamari…"	string
		Source	"Xamarin.iOS"	string
		StackTrace	"  at ObjCRuntime.Runtime.Initialize (ObjCRuntime.InitializationOptions& options) [0x0003c] in <filen…"	string
+		TargetSite	{System.Reflection.MonoMethod}	System.Reflection.MonoMethod
+		Non-public members		
		Code	8001	int
		Error	true	bool
+		Non-public members		
+		options	{ObjCRuntime.Runtime.InitializationOptions}	ObjCRuntime.Runtime.InitializationOptions
		loc0	"Version mismatch between the native Xamarin.iOS runtime and Xamarin.iOS.dll. Please reinstall Xamari…"	string

This unhandled exception is thrown after the splash screen is displayed on iOS (simulator or physical device), but before the main page of the app appears. This blocks all iOS work, so please make high priority and high severity.

A number of people have reported this on the forums, including at:


I am running Visual Studio 2013 Pro, on 64 bit Windows 8.1 Pro.

I can see a Xamarin.iOS.dll in 
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Xamarin.iOS\v1.0
that does not appear to have been updated for a while, so if the update was intended to change that, that may be help identify why the update has caused this problem.
Comment 1 Chris King 2015-05-20 18:03:10 UTC
We'd be happy to help you resolve this issue but first please help us by attaching a reduced reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue. If you'd do this for us we would very much appreciate it. If you are able to reproduce the issue without modifying the platform specific projects that would eliminate a number of possibilities and likely expedite a resolution. 

Warm regards,
Xamarin Forms Team
Comment 2 John Hardman 2015-05-21 05:14:15 UTC
Sorry, no longer able to help on this one. After two weeks with no success at fixing it, I created a new iOS project, and copied my code etc across piece by piece, before deleting the old iOS project. The new one works fine. Other people reported the same problem on the forum, so you could try them.
Comment 3 John Hardman 2015-09-14 12:42:44 UTC
Propose this bug be closed, as now an old version. Very unlikely anybody would be upgrading to it, and the bug showed up during after upgrading.
Comment 4 John Hardman 2015-12-03 18:27:26 UTC
As per previous comment, suggest this bug be closed. It relates to upgrading between two versions that are now old versions.
Comment 5 Paul DiPietro [MSFT] 2016-01-04 16:55:48 UTC
Closing per request.