Xcode 27.0, 27.1 and 27.2 all ship Swift 6.4 (released 15 September 2026); Xcode 26.x projects were built with Swift 6.3 (24 March 2026). Two changes in 6.4 can stop or dirty a build that was clean on 6.3: a computed property with an init accessor and an array or dictionary literal no longer compiles if the getter comes first, and an unused Task { try ... } now warns. The fix for the first is to move the init accessor above get; for the second, store the task or catch inside it. Everything else in 6.4 is additive.
We built the change table below from the Swift 6.4 section of the Swift CHANGELOG and the Xcode 27, 27.1 and 27.2 release notes, then ran a small checker over the Swift sources of 18 React Native library versions from npm (1,027 Swift files) to see how common the two hot spots are in code an RN app actually ships.
Why we did this: the native iOS modules of the Beacon-type banking apps we build, and our Mac apps Nix and QuitAll, are Swift, and everything has to build with Xcode 27 before Apple’s April 2027 SDK cut-off. Earlier steps of the same move: Swift 6 language mode in a React Native app and iOS 26 SDK to 27.2.
What Xcode 27 ships
| Xcode | Swift | Requires | Source |
|---|---|---|---|
| 27.0 | Swift 6.4 | macOS Tahoe 26.6+, Apple silicon only | Xcode 27 notes |
| 27.1 | Swift 6.4 | macOS Tahoe 26.6+ | Xcode 27.1 notes |
| 27.2 | Swift 6.4 | macOS Tahoe 26.6+ | Xcode 27.2 notes |
None of the three notes changes the default language mode, and the 27.1 and 27.2 notes have no Swift compiler entries at all. So the 6.3 to 6.4 jump happens once, when you first open the project in any Xcode 27.
The two changes that can break a clean build
SE-0508: init accessor plus a literal initial value
SE-0508 lets a trailing closure follow an array or dictionary literal, so [String] { "a" } now calls the Array initializer. The parser now reads = [:] { the same way, and the Xcode 27 notes list the fallout as a known issue (180969028): “A computed property with both an init accessor and an array/dictionary literal initial value will no longer compile if the getter is declared before the init accessor.” Apple calls it “a known source break from SE-0508”. The workaround is to declare the init accessor first.

The order Apple’s workaround asks for; treat it as a starting point and compile it against your own target.
Init accessors are rare in app code, and our checker found none in the 18 library versions. Search your own code for @storageRestrictions and init( inside property bodies before you upgrade.
Unused throwing Task now warns
From the 6.4 changelog: throwing unstructured task initializers (Task.init, Task.immediate, Task.detached) “now use typed-throws and will warn if an operation is throwing and the result of the task is not stored or ignored.” The warning group is NoUseUnstructuredThrowingTask. A non-throwing Task { } is unchanged.

The left side is the exact shape we found in expo-video 58.0.14; the right side handles the error where it happens.
This one matters more than it looks. A Task { try ... } whose result nobody reads throws into the void: the error is dropped silently. The warning points at real bugs, so fix them rather than silencing the group. Your options:
- Catch inside the task (right side above), which is usually what you meant.
- Keep the task in a property (
loadTask = Task { ... }) and readawait loadTask.valuewhere the error belongs. - Write
_ = Task { ... }only when dropping the error is a decision, and leave a comment saying why.
If you build with warnings as errors (SWIFT_TREAT_WARNINGS_AS_ERRORS = YES), this warning becomes the build break. SE-0522, also new in 6.4, lets you scope it per declaration with @diagnose(NoUseUnstructuredThrowingTask, as: warning) while you work through the list.
What we found in 18 React Native library versions
We packed the current versions of the Expo modules and RN libraries a banking or media app typically pulls in, plus react-native-screens 4.30.1 and 5.0.0-beta.1, and ran a 41-line Python checker over every .swift file. It flags two things: a Task { } that is not assigned and has a plain try at its own brace level, and init accessors. It also prints each package’s swift_version and swift-tools-version.

Real output of our checker, trimmed to the two counters per library.
What it showed:
- One hit:
ios/VideoPlayer.swiftline 178 in expo-video 58.0.14,Task { try await replaceCurrentItem(with: initialSource) }. Per the changelog that is a warning, not an error, unless warnings are errors for that pod’s target. - No init accessors in any of the 1,027 files.
- 77
Task { }blocks in total; Stripe’s 39 all catch inside. A first version of the checker also flagged a react-native-iap task whose onlytrysits in a nested closure undertry?; the shipped version only looks at the task’s own brace level, so treat its output as a list to read, not a verdict. - Most Expo modules still declare
s.swift_version = '5.9'in their podspecs (expo-audio, expo-camera, expo-file-system, expo-video, expo-local-authentication), while expo-modules-core and expo-image declare'6.0'. With CocoaPods, that value decides the language mode the pod compiles in, independent of your app target. - react-native-screens 5.0.0-beta.1 adds a
Package.swiftwithswift-tools-version: 6.0; 4.30.1 had none.
Between expo-modules-core 57.0.26 and 58.1.0, Sendable mentions went from 104 to 122 and sending from 13 to 19, so library authors are still tightening concurrency annotations, but none of them use 6.4-only syntax yet (~Sendable, @diagnose, anyAppleOS: zero hits).
The rest of Swift 6.4, by how much it touches app code
| Change | Breaks a build? What to do |
|---|---|
Forward references to local variables in closures now rejected consistently (lazy var x = { y } before let y) |
Yes, in the rare shapes the changelog lists. Declare the variable first |
Module selectors in . for library-evolution builds |
No; old workaround flags are disabled. Remove the workarounds; - reverts |
SE-0503 ~Copyable associated types |
Only if you used the experimental Suppressed. Migrate to the accepted syntax |
SE-0493 await in defer |
No. Use it for async cleanup |
SE-0504 with |
No. Wrap cleanup that must finish after cancellation |
SE-0518 ~Sendable |
No. Mark audited non-Sendable base classes |
@available( |
No. Shorter availability for shared iOS and macOS code |
Not a Swift 6.4 change, but it lands in the same Xcode 27 upgrade: the ld64 linker is gone and -ld_classic is no longer supported (165165518), and #Preview code now runs on the main actor (177394870), which removes a class of concurrency warnings in previews. We covered the linker flag in the iOS 26 SDK to 27.2 guide.
Upgrade checklist
- Search for
@storageRestrictions; in every property that also has an= [or= [:]initial value, moveinitaboveget. - Search for
Task {,Task.detached {andTask.immediate {that are not assigned; add ado/catchor keep the handle. - If you turn warnings into errors, decide how pods are treated first: the expo-video task above lives in the pod’s own target.
- Remove
-ld_classicfromOTHER_LDFLAGSin the app and in anypost_installhook. - If you ship an XCFramework with library evolution, drop module-name workaround flags and rebuild the interfaces.
- Rebuild in Xcode 27.2 and read the warning list once with the table above beside it.



