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.
Related to https://bugzilla.xamarin.com/show_bug.cgi?id=59177 we're getting errors like:
`error MM4162: The type 'AppKit.NSAccessibilityCustomAction' (used as the property type of AppKit.INSAccessibility.AccessibilityCustomActions) is not available in macOS 10.12.4 (it was introduced in macOS 10.13)`
when you're using a XM version that ships APIs not available in the currently selected Xcode SDK (e.g XM xcode9 when building an app with Xcode 8.3).
On iOS we have this cute error that we should also have with mmp:
`MTOUCH : error MT0091: This version of Xamarin.iOS requires the iOS 11.0 SDK (shipped with Xcode 9). Either upgrade Xcode to get the required header files or set the managed linker behaviour to Link Framework SDKs Only (to try to avoid the new APIs).`
The it's telling you exactly what do to and that would avoid getting **hundred** of those MM4162 errors.