Bug 1981 - Error appears when click on the .xib file.
Summary: Error appears when click on the .xib file.
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Alan McGovern
Depends on:
Reported: 2011-11-10 06:17 UTC by Jatin
Modified: 2015-08-20 03:24 UTC (History)
4 users (show)

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

Screenshot for the bug. (109.05 KB, image/png)
2011-11-10 06:17 UTC, Jatin

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 Jatin 2011-11-10 06:17:02 UTC
Created attachment 864 [details]
Screenshot for the bug.

Steps to reproduce:

1.Create a MonoTouch project.
2.Double-click on the <Projectname>ViewController.xib file in MonoDevelop.
3.Observe that .xib file does not open, rather an error appears.

Actual Result:

When try to open .xib file error appears, i.e:

Error updating Objective-C type information. Object reference not set to an instance of an object. (Refer to the screenshot)


System.NullReferenceException: Object reference not set to an instance of an object
  at MonoDevelop.MacDev.ObjCIntegration.NSObjectProjectInfo+<GetReferencedProjects>c__Iterator3.MoveNext () [0x00023] in /private/tmp/source/monodevelop/main/src/addins/MonoDevelop.MacDev/ObjCIntegration/NSObjectProjectInfo.cs:76 
  at MonoDevelop.MacDev.ObjCIntegration.NSObjectProjectInfo.Update () [0x00042] in /private/tmp/source/monodevelop/main/src/addins/MonoDevelop.MacDev/ObjCIntegration/NSObjectProjectInfo.cs:88 
  at MonoDevelop.MacDev.ObjCIntegration.NSObjectProjectInfo.Update (Boolean force) [0x0000c] in /private/tmp/source/monodevelop/main/src/addins/MonoDevelop.MacDev/ObjCIntegration/NSObjectProjectInfo.cs:70 
  at MonoDevelop.MacDev.XcodeSyncing.XcodeProjectTracker.UpdateTypes (IProgressMonitor monitor, Boolean force) [0x00034] in /private/tmp/source/monodevelop/main/src/addins/MonoDevelop.MacDev/XcodeSyncing/XcodeProjectTracker.cs:302 

Expected result:

Error should not appear, instead .xib file should open in the Xcode.


Mac 10.7 (Lion) + Mac 10.6 (SnowLeopard)
MonoTouch 5.1
MonoDevelop 3.0 Beta-1 (2.9.0)
Comment 1 Alan McGovern 2011-11-10 06:36:59 UTC
Which project template did you choose? Different project templates use different files so it'll help narrow things down if I know which it was.

It would also help in future if there was an automated way of creating a project for each template and ensuring it builds and they can be opened in xcode, or is that the kind of testcase you were running when you caught this?
Comment 2 Saurabh 2011-11-11 00:45:01 UTC
Hi Alan,

This issue exists for all the project tempelates, whereever the .xib file or .storyboard file exists, this issue also exists. As these file launch Xcode to open its content. i.e. 

1. All the projects under the categories iPhone. For example: 
   iPhone_Single View Application, iPhone_Empty Project, etc.

2. All the projects under the categories iPad.

3. All the projects under the categories Universal.

4. All the projects under all the categories of Storyboard.

Comment 3 Jeffrey Stedfast 2011-11-18 13:39:38 UTC
this is fixed now
Comment 4 Jatin 2011-12-22 10:11:21 UTC
This issue is fixed when tested on the new installers, i.e.

MonoDevelop 2.8.5
MonoTouch 5.0.4
Mono for Android 4.0.1
Mono 2.10.7

Hence, closing this issue.