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.
I'm using MFMailComposeViewController to send emails from our app. After upgrading to ios 7 SDK there is a bug with ios 6 devices.
There is a code example:
var emailController = new MonoTouch.MessageUI.MFMailComposeViewController ();
emailController.Finished += OnEmailControllerFinished;
emailController.SetMessageBody ("body", isHtml: false);
PresentViewController (emailController, true, null);
The email composer is successfully shown and I can send email but if I hit 'Cancel' button (left top), the screen is freezing. It looks like the popup asking to delete draft and save it is shown within wrong parent view. In ios 7 devices it works fine.
* include all version information ; and
* attach a self-contained test case that reproduce the issue 
The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
 It's very common that we can't reproduce issues when creating our own samples due to other differences (either in code, like initialization, or build options). A self-contained test case ensure we're testing the exact same thing (and issue) that you're experiencing.
Are you using a delegate to handle finishing the event? If so, post that information. When you hit cancel something needs to handle that data. If you haven't done that, I am surprised it works in 7.0, which is why I am guessing that you have.
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!