Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
1. Update to the latest version of MonoDevelop (at the time of this writting it's 3.0.2).
2. Update to the latest SDK (at the time of this writing it's 2.10.9).
3. Start New Solution
4. Select "MonoMac Project"
5. Click "Start program without debugging"
6. Hold down Command and press Q - or - Select the name of the application from the menu and select "Quit"
I've followed these step on my Snow Leopard Macbook Pro with an older version of XCode (version information included below) and on my Lion iMac with the latest version of XCode with the same results.
From Macbook Pro:
Installation UUID: aad14cea-1e23-4ad4-b82c-e1b78905053f
Mono 2.10.9 (tarball Mon May 7 20:25:51 EDT 2012)
Package version: 210090011
Apple Developer Tools:
Xcode 4.0.2 (99)
Mono for Android not installed
Release ID: 30002000
Git revision: 046db1bb0d9d438aa4d3468d66c6f963bc44c51a-dirty
Build date: 2012-05-23 21:39:54+0000
Xamarin addins: d99a1741642a336943d5607bdc1a09efa2ac3b86
Mac OS X 10.6.8
Darwin new-host-5.home 10.8.0 Darwin Kernel Version 10.8.0
Tue Jun 7 16:32:41 PDT 2011
Thanks for the bug report!
This is now fixed in git master.
The problem was that "MainMenu" was not being set as the NSMainNibFile in the Info.plist.
*** Bug 5574 has been marked as a duplicate of this bug. ***