Bug 1381 - Cannot open plist
Summary: Cannot open plist
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2011-10-09 14:06 UTC by Anonymous
Modified: 2011-10-12 11:36 UTC (History)
1 user (show)

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

Log from first session after converting project (4.26 KB, text/plain)
2011-10-09 14:41 UTC, Anonymous
log from second session after restarting MD (5.13 KB, text/plain)
2011-10-09 14:41 UTC, Anonymous

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 Anonymous 2011-10-09 14:06:18 UTC
When I double click on my Info.plist MD 2.8 RTM doesn't do anything for several seconds then when it because response again nothing happens.

My expectations now that there is Xcode 4 integration by using Xcode projects under the cover that I should be able to open a plist in Xcode's plist editor, at worse I should be able to view it as raw XML in MD.  However nothing happens at all.
Comment 1 Alan McGovern 2011-10-09 14:28:48 UTC
What version of Mono do you have installed? Also, can you open monodevelop, double click on the info.plist file and then attach the log file found in your home folder in the: Library/Logs/MonoDevelop-2.8 directory. It's called MonoDevelop.log
Comment 2 Anonymous 2011-10-09 14:40:33 UTC
I am always on the latest release, so I am using 2.10.5.

It opened the second time after I relaunched MD.  It seems to be an issue after it first converted my project and while I still had MD open after that conversion.

I saved the log file from that session to compare to the second one.

The only difference between them is:

WARNING [2011-10-09 10:20:42Z]: Gtk-Warning: Could not find the icon 'gtk-find'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:

However The both have a stacktrace in them so I will attached both of them for you to review after this post.

However it is now working after restarting MD which is odd, so I hope the cause can still be found to prevent others form having the issue, although this is not a bad workaround.
Comment 3 Anonymous 2011-10-09 14:41:14 UTC
Created attachment 651 [details]
Log from first session after converting project
Comment 4 Anonymous 2011-10-09 14:41:36 UTC
Created attachment 652 [details]
log from second session after restarting MD
Comment 5 Alan McGovern 2011-10-12 11:25:58 UTC

I can't replicate the issue. Either this is something specific to your project (pretty unlikely), or you were hitting a known issue where double clicking on items in the Solution pane does not work. The workaround for that is simply to click outside of MonoDevelop so the app loses focus. Then when you go back to MonoDevelop it will be responsive again. Does that sound like what might have happened?
Comment 6 Anonymous 2011-10-12 11:31:57 UTC
That is possible, as closing MD also works around the problem.  Since that is a known issue feel free to close this as a dup if you agree, thanks for your help.
Comment 7 Alan McGovern 2011-10-12 11:36:32 UTC
If the issue does show up again and it's not the clicking problem, feel free to reopen this issue and I'll look into it again.

Thanks for the report!