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.
The events on UISplitViewController stopped working in MonoTouch 5.0.4. Specifically the following stopped working:
mySplitViewController.WillShowViewController += SplitViewWillShow;
mySplitViewController.WillPresentViewController += SplitViewWillPresent;
mySplitViewController.WillHideViewController += SplitViewWillHide;
It's easy enough to work around by using a delegate; however the event approach had been working since the beginning. Luckily, I caught this before submitting my next version to Apple for approval.
It's weird because the CoreAnimation sample (from xamarin/monotouch-samples on github) works for me.
Can you tell me what was the last/previous, known to work, version of MonoTouch you used ? and attach a small, self-contained, test case so I can reproduce the issue ?
The last/previous version known to work was 5.0.3. I try to keep up to date on all the upgrades as they come out.
It will take me a day or so to create a small sample, as it was TouchDraw that had these issues and it's a pretty large code base at this point.
Jon, you might want to try the CoreAnimation sample from
if it works then the problem is likely elsewhere (and will make the sample more important)
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.