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.
Created attachment 16214 [details]
Native stack trace
1. Create a custom TableViewController through the storyboard
2. In the custom class that inherits from UITableViewController, override 'WillDisplay' method with the preset code:
public override void WillDisplay(UITableView tableView, UITableViewCell cell, NSIndexPath indexPath)
base.WillDisplay(tableView, cell, indexPath);
3. Code will crash with:
Foundation.MonoTouchException: Objective-C exception thrown. Name: NSInvalidArgumentException Reason: -[myCustomTableViewController tableView:willDisplayCell:forRowAtIndexPath:]: unrecognized selector sent to instance 0x7cd39c30
Hello I tried to reproduce this locally but I was not able to get a crash nor any MonoTouchException. Could you create a self contained test case and attach to this bug report that reproduces this issue?
Also please include your full build logs, crash reports (if any)
and all version informations.
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).
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!