{"id":53201,"date":"2026-09-15T16:55:21","date_gmt":"2026-09-15T20:55:21","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=53201"},"modified":"2026-09-15T16:55:21","modified_gmt":"2026-09-15T20:55:21","slug":"xcode-27","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/09\/15\/xcode-27\/","title":{"rendered":"Xcode 27"},"content":{"rendered":"

Apple<\/a> (xip<\/a>, downloads<\/a>):<\/p>\n

\n

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.<\/p>\n<\/blockquote>\n\n

Peter Witham<\/a>:<\/p>\n

\n

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.<\/p>\n<\/blockquote>\n\n

Christian Beer<\/a>:<\/p>\n

\n

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…<\/p>\n<\/blockquote>\n\n

Steven Woolgar<\/a>:<\/p>\n

\n

After all these years Apple has finally broken cmd-e in Xcode 27.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n