Apple (xip, downloads):

Xcode 27 includes Swift 6.4 and SDKs for iOS 27, iPadOS 27, tvOS 27, watchOS 27, macOS 27, and visionOS 27. Xcode 27 supports on-device debugging in iOS 17 and later, tvOS 17 and later, watchOS 10 and later, and visionOS. Xcode 27 requires a Mac running macOS Tahoe 26.6 or later.

Peter Witham:

Is this new in Xcode 27? Pretty sure it as and I approve whole heartedly! I really hate setting up Xcode settings more than once.

Christian Beer:

Building with Xcode 27 doesn’t work because of some intransparent XCStrings error… and I even can’t check with Xcode 26 anymore because Apple decided to not let me run it on macOS 27…

Steven Woolgar:

After all these years Apple has finally broken cmd-e in Xcode 27.

Previously:

• iPhone Duo
• Ending the Golden Era for Backward-Compatible Apps
• Xcode 26.6
• Xcode 27’s Device Hub
• Swift 6.4
• Xcode 27 Announced

Update (2026-09-18): Jesse Squires:

Xcode 27 seems to have broken UI appearance vs Editor appearance. They used to be separate settings.

For example, previously, the app could be light mode while the editor theme was dark.

But now, you choose a dark editor theme and the whole app goes to dark mode.

I hate this.

Me, too.

Update (2026-09-24): Christian Beer:

• generate stubs for protocol: uses wrong class names
• fix for missing parameter: inserts it at the wrong position
• generating init with Bindings, State, etc.: mostly wrong

Update (2026-10-01): Steve Troughton-Smith:

AI code completion was such a nothingburger, for all of that investment. I don’t even have it turned on in Xcode anymore. If you’re into code completion, you’re into using Codex and Claude, so why would you ever use it now.

The built-in Xcode stuff has pretty much never worked at all for me. I either get errors or it does nothing.

macOS 26.7 (security, no enterprise, no developer, full installer):

This update provides important security fixes and is recommended for all users.

macOS 15.8 (security, full installer):

This update provides important security fixes and is recommended for all users.

See also: MacRumors, Mr. Macintosh, and Howard Oakley.

Previously:

• macOS 27 Golden Gate
• macOS 26.6.2
• macOS 15.7.9 and 14.8.9

Update (2026-09-22): Wade Tregaskis:

Yesterday I tried doing the 15.8 update (from 15.7.9) inside one of those VMs. It hanged, midway through the post-reboot install process. I had to ‘power-cycle’ the VM. Which booted it back into 15.7.9, except… shockingly slow. Like, I can watch the individual elements of the GUI render like it’s the 1980s again.

I eventually figured out that my 16 GiB VM could only “see” 1.75 GiB of RAM, and was therefore swapping all to hell.

[…]

In hindsight, the simplest solution might be – I have not tested it – to just run:

sudo nvram -d boot-args

That should clear the boot args, eliminating whatever insane stupidity Apple’s updater enacted there.

me22 (via david_blanchard):

Apple’s camera raw support seems to be broken here since updating to macOS 15.8.0.

Update (2026-09-23): Brian Webster:

I can corroborate there being a problem with RAW files on macOS 15.8. I’ve had two customers run into problems trying to copy RAW images with PowerPhotos, it appears that photolibraryd ends up deadlocked somewhere in the RawCamera library, and you have to kill it to get things moving again.

Update (2026-09-25): Norbert M. Doerner:

Apple was able to completely break the essential RawCamera system framework, and macOS 15.8 is now unable to use Nikon, Canon, and other RAW files anymore.

[…]

Spotlight will hang for CR2, NEF, or DNG and other files, Preview.app can no longer open RAW files and will hang forever. The Finder can no longer display thumbnails of RAW files and will hang trying to do so. As will all other applications that can open these RAW files directly, like Apples own Pages.