Bug 6847 - Errors after setting Main Interface drop down in plist
Summary: Errors after setting Main Interface drop down in plist
Status: RESOLVED DUPLICATE of bug 999
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-09-02 21:35 UTC by Mike McDougall
Modified: 2012-11-15 12:55 UTC (History)
2 users (show)

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 Mike McDougall 2012-09-02 21:35:21 UTC
If you have any outlets on your view after you set Main Interface in the plist file app compiles but crashes when running with this error - this class is not key value coding-compliant for the key.

Workaround - Clear values from Main Interface dropdowns.
Comment 1 Jeffrey Stedfast 2012-09-21 14:09:53 UTC
I'm not sure there is anything we can do to "fix" this... we don't want to be ripping stuff out of a user's .xib file behind their backs :-\

Perhaps we can update documentation to explain this problem and the solution?
Comment 2 Jeffrey Stedfast 2012-11-15 12:55:53 UTC

*** This bug has been marked as a duplicate of bug 999 ***