This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can trysigning in orchanging directories.
Access to this page requires authorization. You can trychanging directories.
Getting Started |What's New |Known Issues |Blogs |Feedback |Open Source
For more information you can consult theXcode 10 release notes from Apple.
The following new frameworks were added in iOS 12:
Most other frameworks were also updated, including ARKit 2.0 and Siri (Intents) shortcuts. See ourAPI diff to browse the newest API.
For more information you can consult theiOS 12 release notes from Apple.
The following new frameworks were added in tvOS 12:
Most other frameworks were also updated. See our [API diff](#api-diff to browse the newest API.
For more information you can consult thetvOS 12 release notes from Apple.
The following new frameworks were added in watchOS 5:
Most other frameworks were also updated. See ourAPI diff to browse the newest API.
For more information you can consult thewatchOS 5 release notes from Apple.
TheGC pump thread used on simulator builds is nowdisabled by default. This feature was added, a long time ago, to help diagnose object instances without managed references, where the GC could collect them and cause randomly occurring, hard to diagnose crashes. However it can causeissues when debugging applications. Since several changes over the years made this option less useful it is nowdisabled and, if needed, can be re-enabled by adding--debugtrack:true to themtouch additional arguments of your project's options.
This version of Xamarin.iOS correspond to ourxcode10 milestone and is based of the stable15.8 release.
Earlier release notes, for Xamarin.iOS previews for Xcode 10 betas, are located inXamarin.iOS 11.99.
This release is based on the Xcode 10 final release.
This release is based on the Xcode 10 GM seed.
Xcode 10 GM added support for 64 bits watch application, akaarm64_32. The current app store submission processrequires this architecture to be included in your application when including watch support. You can workaround this with [https://github.com/xamarin/xamarin-macios/issues/4810#issuecomment-421338365](these instructions).
Trying to run a watch app on the new Series 4 Apple Watch will fail with this error:
IncorrectArchitecture: Failed to find matching arch for 32-bit Mach-O input file ...error MT1006: Could not install the application 'MyTestApp.app' on the device 'MyDevice': AMDeviceSecureInstallApplicationBundle returned: 0xe8000087 (kAMDIncorrectArchitectureError).This is because the S4 device can only execute nativearm64_32 code, notarmv7k like previous watches.
Please readhttps://github.com/xamarin/xamarin-macios/issues/4864 for more information and a workaround.
stdlibc++. Using C++ code now requires the use oflibc++.TVElementUpdateType* enum values. Please test your application if you're usinf this type.IN*WorkoutIntentResponseCode enum values. Please test your application if you're usinf this type.RPBroadcastPickerView symbol is not present in simulator. If needed you'll need to test this on devices.ld to process properly. The workaround is to enable the managed linker (e.g.Link SDK) on your projects.Using an older Xcode version (than the one mentioned in the aboverequirements) is often possible, but some features may not be available. Also, some limitations might require workarounds, e.g.:
MT0091 orMT4109 errors if API are missing. In most cases enabling the managed linker will help (by removing the API).The following documents contains a complete list of the API changes since the Xamarin.iOS 11.14 stable release:
Your feedback is important to us. If there are any problems with this release, check theXamarin.iOS Forums andGithub Issues for existing issues. If you do not find any matching issue, please feel free tostart a new discussion andreport an issue.
Xamarin.iOS is based on the following open-source repositories:
xcode102018-02