Bug 5606 - Error synchronising from Xcode
Summary: Error synchronising from Xcode
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-06-11 05:25 UTC by Dylan
Modified: 2013-04-02 16:58 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

references in the problematic solution (42.28 KB, image/png)
2012-06-13 16:54 UTC, Dylan

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 Dylan 2012-06-11 05:25:37 UTC
System.ArgumentException: Multiple types (MonoTouch.CoreTelephony.CTCall and MonoTouch.CoreTelephony.CTCall) registered with the same Objective-C name: CTCall
  at MonoDevelop.MacDev.ObjCIntegration.NSObjectProjectInfo.Update () [0x00000] in <filename unknown>:0 
  at MonoDevelop.MacDev.ObjCIntegration.NSObjectProjectInfo.Update (Boolean force) [0x00000] in <filename unknown>:0 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeSyncBackContext.get_ProjectInfo () [0x00000] in <filename unknown>:0 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeSyncBackContext.MergeExistingTypes (System.Collections.Generic.Dictionary`2 designerFiles) [0x00000] in <filename unknown>:0 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeSyncBackContext.GetTypeUpdates (IProgressMonitor monitor, System.CodeDom.Compiler.CodeDomProvider provider, System.Collections.Generic.Dictionary`2& newTypes, System.Collections.Generic.Dictionary`2& newFiles) [0x00000] in <filename unknown>:0 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeProjectTracker.UpdateCliTypes (IProgressMonitor monitor, MonoDevelop.MacDev.XcodeSyncing.XcodeSyncBackContext context, System.Boolean& typesAdded) [0x00000] in <filename unknown>:0 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeProjectTracker.SyncXcodeChanges (IProgressMonitor monitor) [0x00000] in <filename unknown>:0
Comment 1 Mikayla Hutchinson [MSFT] 2012-06-11 20:21:29 UTC
What MonoDevelop version are you using?
Comment 2 Dylan 2012-06-12 05:38:58 UTC
Version from the beta channel.
Comment 3 Jeffrey Stedfast 2012-06-13 14:32:56 UTC
fixed in git master and backported to the 3.0 branch (so if another 3.0.3 is rolled, it'll be in it)
Comment 4 Mikayla Hutchinson [MSFT] 2012-06-13 15:00:44 UTC
The fix is for the error, not the underlying issue.

Dylan, does your project somehow have multiple references to MonoTouch.dll?
Comment 5 Dylan 2012-06-13 16:54:52 UTC
Created attachment 2053 [details]
references in the problematic solution
Comment 6 Dylan 2012-06-13 16:55:23 UTC
I have attached a screenshot of the references in the problematic solutions. I hope this answers your question.
Comment 7 Jeffrey Stedfast 2012-06-13 17:08:05 UTC
yes, it does. Thanks Dylan.

This is what I suspected was the cause.
Comment 8 Mikayla Hutchinson [MSFT] 2012-06-14 00:29:12 UTC
Jeff, what am I missing? I don't see any duplicated references there.
Comment 9 Jeffrey Stedfast 2013-04-02 16:52:50 UTC
Have you had this happen since the release of Xamarin Studio?
Comment 10 Dylan 2013-04-02 16:56:20 UTC
I haven't experienced this since Xamarin Studio no. Great job on the IDE! I think this issue can be closed.
Comment 11 Jeffrey Stedfast 2013-04-02 16:58:03 UTC
ok, cool, and thanks!