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 2093 [details]
See attached test case.
* Run test case.
* Tap somewhere.
Selector not found exception will be thrown.
* Change MyView.HandleTap from private to internal and try again.
Note how no exceptions are thrown now.
This comes from http://lists.ximian.com/pipermail/monotouch/2012-June/010089.html
The nasty issue is that you can have a class that's working perfectly fine, but then you create a subclass (without any code at all inside it), and suddenly that subclass doesn't work.
FWIW, this seems the same as bug 1449.
If someone has exported a member, they have explicitly made it public to Obj-C, even if it's private to C#. Having such things break as soon as they're subclassed isn't useful or consistent at all, IMO.
This has been fixed in the new registrar.