Bug 5463 - Couldnt open .xib files in Xcode from MD using Xcode 4.2.1 and Mono 2.10.9_11
Summary: Couldnt open .xib files in Xcode from MD using Xcode 4.2.1 and Mono 2.10.9_11
Status: RESOLVED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-06-01 16:36 UTC by PJ
Modified: 2012-06-09 04:01 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED INVALID

Description PJ 2012-06-01 16:36:32 UTC
Environment:

Lion 10.7.4
Xcode 4.2.1 (834)
MT 5.2.12
Mono 2.10.9_11


Steps to reproduce:

Create (example) iPad->Single View Application
Double click the .xib file

Expected Result:
Xcode opens

Actual Result:
https://gist.github.com/2854908
Comment 1 PJ 2012-06-01 16:41:55 UTC
This issue does not occur on Mono 2.10.9_10
Comment 2 PJ 2012-06-01 16:56:04 UTC
I couldn't reproduce this after re-upgrading to 2.10.9_11 

I still have the snapshot where this error occurs and the version info is the same.

Screencast:
http://screencast.com/t/FaldohBVuMDf

Version info (full):
https://gist.github.com/2855075


Makes this much more confusing. Any thoughts?
Comment 3 Mike Krüger 2012-06-04 03:44:02 UTC
There is something wrong with a dll I suppose. I've added a better description to the exception. Can you update the MD to a build of today and try again - (the new exception message may help me) ?

(or can you give me the mono package where that happens ?)
Comment 4 PJ 2012-06-04 03:54:46 UTC
Thanks! Will do that tomorrow in the light of day.

In the meantime I'm lowering the severity because I was able to work around the issue by re-installing.
Comment 5 Mike Krüger 2012-06-07 03:08:21 UTC
any news on that ?
Comment 6 TestRail Defect Push 2012-06-07 18:52:16 UTC
I've had to put this on the backburner as it seemed to be solved by re-installing and more pressing tasks are at hand. Will keep this on my plate to try to reproduce, but I have a feeling that just by installing the new build I'll have 'fixed' the environment.
Comment 7 Mike Krüger 2012-06-09 04:01:44 UTC
Ok setting it to fixed. Something was wrong with the DLL, I would've liked to know what.