Xcode 26.2
Xcode 26.2 includes Swift 6.2.3 and SDKs for iOS 26.2, iPadOS 26.2, tvOS 26.2, macOS 26.2, and visionOS 26.2. Xcode 26.2 supports on-device debugging in iOS 15 and later, tvOS 15 and later, watchOS 8 and later, and visionOS. Xcode 26.2 requires a Mac running macOS Sequoia 15.6 or later.
[…]
You can now annotate C types with the
SWIFT_SHARED_REFERENCEattribute.[…]
Retain and release operations for
SWIFT_SHARED_REFERENCEtypes can now be methods of the type. You can now annotate a C/C++ type withSWIFT_SHARED_REFERENCE(.doRetain, .doRelease)to use methodsdoRetainanddoReleaseas the lifetime operations for the type.
Nothing about the simulator and visionOS issues.
Previously:
Update (2026-01-07): Christian Tietze:
My Xcode 26.2 still suffers from an inability to compile Metal shader files because it can’t find the Metal toolchain[…] But I did have success mounting the
.dmgfile with the toolchain manually.
Update (2026-01-08): Rob Napier:
I have a Swift macro that wraps
OSLog(which is, considered the appropriate way to do this), and I swear “jump to source” used to work fine with it (the whole reason for building the macro was to keep this support) But in Xcode 26.2, it’s linking to stuff like…/@__swiftmacro….logError…_.swift:3:8and you can’t jump with it.
I haven’t followed any conversation about this, but in Xcode 26, it seems like navigation history extends across tabs you’ve navigated to.
Example: if switch from tab A to tab B, and then hit “Back”, it just opens tab A again.
I’ve given this behavior six months, and it’s just maddening. Is there a way to revert this to the old way?
Update (2026-01-14): Casey Liss:
I can’t do it anymore. I’ve tried, but it’s just so fucking inscrutable.
How do I go back to the sensible tab handling mechanism in Xcode 26?
2 Comments RSS · Twitter · Mastodon
The MercuryPosterExtension issue with the iOS 26.1 simulator was resolved with a re–submission of the simulator runtime, they published a new build a few days later for that issue.
