# Xcode 10.1 Migration

DevFeed: [Xcode 10.1 Migration](<https://devfeed.tech/articles/xcode-10-1-migration-19679.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/xcode-10-1-migration/>)

Author: Shai Almog

Published: 2019-01-08T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [migration](<https://devfeed.tech/topics/migration.md>), [Xcode](<https://devfeed.tech/topics/xcode.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [bugs](<https://devfeed.tech/tags/bugs.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [ios](<https://devfeed.tech/tags/ios.md>), [migration](<https://devfeed.tech/tags/migration.md>), [regression](<https://devfeed.tech/tags/regression.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [xcode](<https://devfeed.tech/tags/xcode.md>)

## AI overview

Codename One plans to update its servers to Xcode 10.1 in response to Apple warnings about older SDKs. The article notes that migration-related bugs or regressions may occur and provides a build hint to force Xcode 9.2 for compatibility testing.

## Source excerpt

Over the past month Apple started sending out warnings that they will no longer accept apps built with older SDK's starting this March. To preempt that we will update our servers to use xcode 10.1 over the next couple of weeks. This change should be seamless for the most part but some odd behaviors or bugs usually rise as a result of such migrations. To test if a sudden regression is caused by this migration you can explicitly force xcode 9.2 for compatibility by using the build hint: ios.xcode_version=9.2.