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.
A method with an ObjC parameter type NSObject<MyProtocol> * will map to a C# type of NSObject<MyProtocol>, but it should be just MyProtocol. Here's an example from trying to bind Crashlytics.framework:
// @interface Crashlytics : NSObject
// +(Crashlytics *)startWithAPIKey:(NSString *)apiKey delegate:(NSObject<CrashlyticsDelegate> *)delegate;
Crashlytics StartWithAPIKey (string apiKey, NSObject<CrashlyticsDelegate> @delegate);
// @protocol CrashlyticsDelegate <NSObject>
Fixed. ObjC protocols with a single qualifier will be promoted to a concrete interface. Protocols with multiple qualifiers will be bound as NSObject<> generic types, which AFAIK are actually not valid currently in Xamarin iOS/Mac, but at least from a binding auditing perspective is more clear - the user can verify to which qualifier the type should promote.