Xcode 27 is out, and the change most likely to surprise an iOS team is that some of its CI machines can no longer run it at all. Apple's Xcode 27 release notes confirm the toolchain now bundles Swift 6.4 and SDKs for iOS 27, iPadOS 27, tvOS 27, watchOS 27, macOS 27, and visionOS 27, and it needs a Mac running macOS Tahoe 26.6 or later to install at all. On-device debugging now needs iOS 17, tvOS 17 or watchOS 10 or later (plus visionOS), so any team holding onto an older test device for legacy coverage needs a plan before this upgrade lands.
The bigger problem is any Intel Mac still sitting in your build fleet.
Apple silicon only: what this means for your CI machines
Xcode 27 will only install and run on Apple silicon Macs, according to Apple's release notes under Intel Deprecation. Any Intel build machine in your fleet is out, with no exceptions in the notes.
If your CI fleet still has Intel runners doing real work, this is the line item that needs budget attention before your next release cycle, not after a build starts failing mid-release. The macOS 27 SDK still supports back-deploying Universal apps, both Intel and Apple silicon, down to macOS 12, and Intel development stays possible on a Mac running macOS 27 through Rosetta. You can keep shipping to Intel Mac users. You just can't build on an Intel Mac to do it.
Your default Universal build just lost x86_64
There's a second, narrower change in the same section, and it's easy to misread. Apple scoped it specifically to macOS and DriverKit targets: build targets with a minimum deployment target of macOS 27.0 or DriverKit 27.0 will not build Universal by default, and the ARCHS_STANDARD setting no longer includes x86_64 once MACOSX_DEPLOYMENT_TARGET or DRIVERKIT_DEPLOYMENT_TARGET reaches 27.0 or above. It applies to macOS and DriverKit builds only, not to iOS, tvOS, watchOS or visionOS targets at 27.0. If one of those affected targets still needs x86_64 in the shipped binary, Apple's fix is straightforward: add it back explicitly through the ARCHS build setting.
Swift 6.4 rides along, but its build-system risk is a separate story
Xcode 27 bundles Swift 6.4, and the change in that release most likely to hit your CI pipeline isn't an Xcode setting at all: Swift 6.4 made Swift Build the default build system in Swift Package Manager. That's a big enough shift on its own, with its own set of SwiftPM issues and workarounds, that it earns its own read rather than a summary here.
What else to audit before you upgrade
The same release notes page lists several deprecations that won't make headlines but will break a build or a test target if you don't catch them first.
The ld64 linker is gone. The -ld_classic fallback option is no longer supported, so any build script or CI config still forcing the old linker will need changing, because that fallback no longer exists.
PreviewProvider and its family of preview modifiers are deprecated. If your SwiftUI views still use the old preview protocol instead of the #Preview macro, budget time to migrate while it's only deprecated.
Instruments raised its floor. Profiling now requires target devices running at least iOS 17, watchOS 10, or tvOS 17, which strands any performance work you're still running against older test hardware.
Device Hub did the same for input. Keyboard and pointer interactions there now need macOS 15, iOS 18, tvOS 18, watchOS 11, or visionOS 2 at minimum.
On Demand Resources and the NSBundleResourceRequest API are deprecated too, with Apple pointing teams to Background Assets instead. That's a real migration project if you lean on ODR for large asset bundles today, not a settings toggle.
The April 2027 App Store SDK deadline
Apple has also set a deadline for anyone shipping to its stores. Starting in April 2027, Apple's developer news states that apps and games uploaded to App Store Connect need to meet new minimum SDK requirements: iOS and iPadOS apps built with the iOS 27 or iPadOS 27 SDK or later, tvOS apps with the tvOS 27 SDK or later, visionOS apps with the visionOS 27 SDK or later, and watchOS apps with the watchOS 27 SDK or later. Apple hasn't published an exact day, only the month, so treat April 2027 as the outer edge of your planning window rather than a date to cut close.
If your team ships to both stores, this deadline doesn't sit in isolation. Google set its own SDK floor for Android earlier in 2026, requiring new apps and updates to target API level 36 or higher. Put both deadlines on the same release calendar rather than tracking them separately, since a cross-platform release train that misses one is usually close to missing the other.
How to prepare your CI and team for Xcode 27
1. Confirm your CI runners are Apple silicon
Check every machine in your build fleet, self-hosted or a provider's shared pool, for architecture, not just macOS version. An Intel Mac running the latest macOS still can't install Xcode 27. Replace any that are still doing real work before one of them becomes the build that fails on release night.
2. Audit ARCHS/deployment targets for any Universal build you still need
Search your project for MACOSX_DEPLOYMENT_TARGET and DRIVERKIT_DEPLOYMENT_TARGET settings at 27.0 or above. If any of those targets still need x86_64 in the shipped binary, add it back explicitly in ARCHS rather than assuming it's still there by default.
3. Grep your project for -ld_classic, PreviewProvider, and NSBundleResourceRequest
Catch all three in one pass now instead of chasing three separate failures after the upgrade.
4. Check your minimum simulator/device OS versions against the new debugging floor
If your test matrix or CI simulator config still targets devices below the new Instruments and Device Hub floors, Instruments profiling and Device Hub input testing won't be available on those devices.
5. Put the April 2027 SDK deadline on your release calendar
Set a milestone well ahead of April 2027 to confirm your build is on the required SDK for every platform you ship to. If you also ship Android, line it up against the API 36 deadline on the same calendar.
An upgrade this disruptive is also a reasonable moment to check whether your roster matches the toolchain. HighCircl's guide to testing iOS candidates on Swift 6 concurrency and data safety is worth reading before your next req goes out. If the audit above turns up a gap you can't close in-house, you can hire vetted iOS engineers ready to start in days rather than months.
FAQ
Can I install Xcode 27 on an Intel Mac?
No. Apple's release notes state plainly that Xcode 27 will only install and run on Apple silicon Macs. There's no workaround at the installer level. You can still develop for Intel through Rosetta on a Mac running macOS 27, but the machine doing the building has to be Apple silicon.
Do I need to change my ARCHS setting if I don't build for macOS or DriverKit?
No. The x86_64 change only affects targets with a MACOSX_DEPLOYMENT_TARGET or DRIVERKIT_DEPLOYMENT_TARGET of 27.0 or later. iOS, tvOS, watchOS, and visionOS builds aren't in scope, so leave your ARCHS setting alone unless you also ship a macOS or DriverKit target.
Does Xcode 27 change Swift's default build system?
Not directly through Xcode. The change comes from Swift 6.4, which Xcode 27 bundles: Swift Build is now the default build system in Swift Package Manager. That's a separate migration with its own set of issues worth reading up on before you hit it in CI.
When exactly do I have to submit apps built with the iOS 27 SDK?
Apple has set the requirement for April 2027, with no exact day published yet. Starting then, apps and games uploaded to App Store Connect need to be built with the SDK matching their platform: iOS 27 or iPadOS 27 for iOS/iPadOS apps, tvOS 27, visionOS 27, or watchOS 27 for those respective platforms.