Xcode 27 on an Intel Mac: what still works after April 2027

Xcode 27 runs only on Apple silicon, and from April 2027 iOS uploads need the iOS 27 SDK. The newest Xcode each Intel Mac can run, what it can still do, and three ways to keep shipping.

November 6, 2026 · 7 min read

Need a Mac for this? NoMac gives your agent full macOS with Xcode for $0.90 an hour, billed per minute. Start now →

If your iOS releases come from an Intel Mac, Apple has now set the month they stop: April 2027. Here are Apple's exact words, the newest Xcode each Intel Mac can run, what the Mac is still good for afterwards, and what the ways to keep shipping cost.

What Apple said

The Xcode 27 release notes:

“Xcode 27 will only install and run on Apple silicon Macs.”

Apple's developer news post of September 9, 2026, about macOS:

“macOS 26 is the final release supporting Intel Mac computers” and “macOS 27 will be Apple silicon only.”

The same post, about uploads:

“Starting April 2027, apps and games uploaded to App Store Connect need to meet the following minimum requirements: iOS and iPadOS apps must be built with the iOS 27 & iPadOS 27 SDK or later”

The list goes on with tvOS, visionOS and watchOS apps, each with its 27 SDK. It does not name macOS apps.

Put together: an Intel Mac stops at macOS 26 and Xcode 26, and from April 2027 App Store Connect does not take an iOS or iPadOS build made with Xcode 26. A TestFlight build is an upload to App Store Connect too, so the rule covers it.

Apple has not said which day in April. Asked on its forums whether Xcode 26 builds would still be accepted in March 2027, an Apple DTS engineer answered that “per policy, we are unable to disclose, confirm, or comment on exact dates for future SDK requirements and App Store submission cutoffs before they are officially announced.” The rule in force now (Xcode 26 and the iOS 26 SDK) took effect on April 28, 2026. Plan for April 1.

Apple's forum thread Xcode 27 for Intel Macs, with over 6,000 views, gets as far as quoting the release note. Nobody in it says what to do next.

The newest Xcode your Intel Mac can run

It depends on the newest macOS the Mac gets. Apple's Xcode requirements page gives each version's minimum macOS, and Apple's compatibility lists for macOS Tahoe and macOS Sequoia say which Intel Macs get there:

Xcode 26.6, from June 2026, is the newest 26.x release in Apple's release notes; every release since is 27.x. Xcode 26 comes as two downloads, one for Apple silicon and a Universal one, and an Intel Mac needs the Universal file (Xcode_26.6_Universal.xip; xcodereleases.com lists both). Keep it installed.

Until the April day, both of those Xcode versions make builds App Store Connect accepts: today's floor is the iOS 26 SDK, and 26.2 and 26.5 both count.

What the Intel Mac can still do

• ·Until April 2027, everything it does today, if it is in the table's first two rows: the release build and the upload included.
• ·After that, everything but the build you upload. You can write and edit code in Xcode 26, run Swift packages and unit tests, and check screens in the iOS 26 Simulator. The build you ship needs Xcode 27, with Swift 6.4 and the iOS 27 SDK (Xcode 26.6 has Swift 6.3), so treat that build as the one that decides.
• ·It cannot catch what only the iOS 27 SDK enforces. The big one is the scene lifecycle: a UIKit app whose AppDelegate owns the window does not launch when built with the iOS 27 SDK (see what iOS 27 changes for shipping). The same app built with Xcode 26 launches fine and tells you nothing.
• ·Mac apps are a different case. Apple's April 2027 list does not name them, and Xcode 27 still builds for Intel: “The macOS 27 SDK supports back deploying Universal (Intel and Apple Silicon) apps to macOS 12 and later.” If you ship a Mac app to Intel users, the Intel Mac stays useful as the machine you test that half on.
• ·Everything that is not Xcode: App Store Connect in a browser, TestFlight on your iPhone, Android, web and server work. It can also drive a Mac somewhere else: the nomac CLI below runs on it.

Three ways to keep shipping

1. Buy an Apple silicon Mac

Apple's cheapest Mac mini is $899 (M6, 16 GB memory, 256 GB storage) in Apple's US store, checked November 4, 2026. It does not have to be new: Xcode 27 needs macOS Tahoe 26.6 or later, and Apple's Tahoe list includes every Apple silicon Mac back to the M1 models of 2020.

If you build most days and keep the machine for years, it is the cheapest Mac per hour. You also look after it: macOS and Xcode updates, disk space, certificates.

2. Let CI make the release build

GitHub Actions charges $0.062 a minute for a standard macOS runner, whether it runs on M1 or Intel. Pick an Apple silicon runner: Xcode 27 does not run on the Intel ones. Standard runners are free in public repositories. In private ones, the $12 a month included with GitHub Free covers about 190 macOS minutes, and the $18 with Pro about 290.

Xcode Cloud comes with 25 compute hours a month in the Apple Developer Program, and 100 hours cost $49.99 a month. The builds run on Apple's machines.

What CI costs you is the setup: certificates, profiles and an App Store Connect key in its secrets, and a workflow that archives and uploads. Once that works, a release is a push. When it fails, you debug from logs. NoMac also sells macOS runners for GitHub Actions, at 1.5¢ a minute: see NoMac CI.

3. Rent a Mac for release days only

If you release once or twice a month, you need macOS for the length of an archive and an upload, which is the case for paying per minute. One option is ours, NoMac: a cloud Mac with Xcode 27 for $0.90 an hour, billed per minute from prepaid credit, with no subscription. Half an hour costs 45¢, and four one-hour release days a month cost $3.60. The price of the Mac mini above buys about 999 hours.

It works the same from Windows, Linux or the Intel Mac itself, with Node 20 or newer. Connect Apple once at nomac.app/apple: your App Store Connect key stays on NoMac's server. Then, from the project folder:

npm install -g @nomac/cli
nomac login                  # approve this device in your browser
nomac start                  # a Mac with Xcode 27, ready in about a minute
nomac sync .                 # this folder, to ~/drive/src on the Mac
nomac exec -- xcodebuild -version
nomac sign                   # App Store profiles, plus the archive and export commands
# run the printed commands with nomac exec --wait 600 -- ...
nomac testflight build/MyApp.ipa
nomac stop                   # deletes the VM; ~/drive stays

A session stops itself after two hours, ten idle minutes or $5 of credit, whichever comes first (--max-duration, --idle-timeout, --max-cost). The project and its build cache stay on the account's 20 GB drive, so the next release day starts from an incremental build. A coding agent can do all of it over MCP: claude mcp add nomac -- npx @nomac/cli mcp.

What it is not: a session is a VM, not a whole Mac, so a large project compiles faster on dedicated hardware. Other services rent by the day or the month (see every cloud Mac compared), and some still rent Intel Macs: AWS's mac1 instances are Intel Core i7 Mac minis, which cannot run Xcode 27. Check the chip before you pay.

Hackintosh and macOS VMs

A Hackintosh is a PC running the Intel version of macOS, and a macOS VM on an Intel or AMD PC runs that same Intel version. Both stop where Intel Macs stop, at macOS 26 and Xcode 26, because macOS 27 has no Intel version. Digital Trends called it the end of the Hackintosh era in June. More in running macOS in a VM on Windows.

Before April

• ·Keep Xcode 26.6 (26.3 on Sequoia) on the Intel Mac. It uploads until the April day.
• ·Make one build with Xcode 27 on Apple silicon now, before you have to. It shows whether the scene lifecycle or anything else in the iOS 27 SDK breaks your app.
• ·Move the release build, and the signing with it, to an Apple silicon Mac, CI or a rented Mac.
• ·Watch Apple's developer news for the exact day.

For what needs a Mac at all, and what does not, see what actually needs a Mac.