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 3151 [details]
Created a Picklist helper classes, but due to JIT compiler issues I had to have a helper for int type picklists and one for string type picklists. They inherit from the same template base class witch intern inherits from UITextField. The problem manifests when both types of picklist helpers are used in the same UIViewController. This problem only occurs on an actual device and not on the simulator. I have attached small test project that demonstrates the problem.
Exporting generic types to ObjectiveC is currently an unsupported scenario.
When building for device this is reported as build warnings:
warning MT4112: The registrar found a generic type: TemplateTestApp.PicklistHelperBase`1. Registering generic types with ObjectiveC is not supported, and will lead to random behavior and/or crashes.
warning MT4112: The registrar found a generic type: TemplateTestApp.PicklistHelperBase`1/PicklistViewController. Registering generic types with ObjectiveC is not supported, and will lead to random behavior and/or crashes.
We already have a bug report open about adding support for exporting generic types to ObjectiveC, so I'm marking this bug as a duplicate of that one.
*** This bug has been marked as a duplicate of bug 6963 ***