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.
Although `CIAreaHistogram` and `CIHistogramDisplayFilter` are bound, it appears that the following filters in Apple's "CICategoryReduction" are missing bindings:
Are you sure they are available on iOS ?
I see them documented to be Mac only  and we have tests that detect what Apple "exports" and match that to our strongly bound versions.
Now it might be that the test is incomplete (and that those requires extra steps to be enumerated)...
No, I'm not sure, but I *do* know that CIAreaHistogram and CIHistogramDisplayFilter are available (and working). Those types, too, seem to be only documented as being available on OS X at the Apple Library page you link. For instance, under CIAreaHistogram, it lists "Availability Available in OS X v10.5 and later."
Yes, Apple doc is kind of bad regarding which filters are available. The published API diff never list them and even the tracking doc  is not very helpful (but does list some mistakes).
FWIW both `CIAreaHistogram` and `CIHistogramDisplayFilter` were added because our introspection tests "found" them :-) which is why I was curious if you had found any resource stating something else (unreported) was available (as it's our only line of defence ;-)
I'll have a look if we can create valid instance of those types (just to be 100% sure) but I do hope our tests are correct :)
I just wrote my own test confirming they are not available to Swift either. So I think you are correct...
I don't recall if I already reported those two cases to Apple (they don't email you back, or even your request) when you give feedback, so I did it again.