Bug 39893 - CIDetectorOptions missing Orientation
Summary: CIDetectorOptions missing Orientation
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 9.8 (tvOS / C7)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-03-24 16:48 UTC by James Prankard
Modified: 2016-03-30 00:28 UTC (History)
3 users (show)

Tags: CIDetector, CIDetectorOptions, iOS, Face, Face Detection
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description James Prankard 2016-03-24 16:48:37 UTC
When instantiating a CoreImage.CIDetector() you can pass in CIDetectorOptions.
However it's missing a key from the original docs.

The key that is missing is 'CIDetectorImageOrientation' which contains an integer between 1 and 8.

This is useful when wanting to pass in an image taken from the camera, as it might be rotated into a different orientation. Faces do not get detected when images are the wrong orientation.

Your docs:

iOS docs:

If it's missing for a reason, could you just update your docs appropriately to say that it's supposed to be missing.

Thanks :)
Comment 1 Alex Soto [MSFT] 2016-03-30 00:28:41 UTC
Thank you James it has been fixed.

Fixed in maccore master @ c4a358a070cc9f4807bc805ed2c81905dd5f3704