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.
In the Intents namespace, INPersonHandle has a nullable "Label" : A standard label that describes the meaning of the information.
That Label  property is of type INPersonHandleLabel , which is an NSString-based enum (in ObjC) and an enum in C#.
@Larry does the API accept other values of NSString ?
In that case we could expose the (protected) `WeakLabel`, which is an `NSString`.
If I read the API correctly, the string should be restricted to the constants defined by INPersonHandleLabel, so IMO it should not be the `NSString` but should be `INPersonHandleLabel` enum.
ok, then it seems to be what we have
If you don't see it inside Xamarin.iOS.dll then please tell us which version you're using.
@Larry can you please confirm what @Sebastien pointed?
Yes, @Sebastien is correct. The defect must have been in an earlier version. The API is now correct.
closing per comment #5