Swift 6 concurrency errors are the most expensive English text a macOS developer reads. A single MainActor isolation mistake can produce a wall of text spanning twenty lines, each a separate diagnostic with its own file and line reference. You copy it, lose a few lines to the wrapping, and now your clipboard holds an error message instead of the fragment you were about to paste.
This is a triage flow for Xcode 16 / Swift 6 diagnostics that keeps you inside the IDE: read the root diagnostic first, work out which concurrency shape it is, then fix code.
The four shapes behind most walls of text
-
Isolation violation —
mutation of captured var 'x' in concurrently-executing code. A captured value is mutated across actor boundaries; the note underneath names the isolation the closure requires. -
Sendable conformance —
type 'Foo' does not conform to the 'Sendable' protocol. Something crosses an isolation domain while holding non-Sendable state. -
Global actor mismatch —
main actor-isolated property 'y' can not be referenced from a nonisolated context. Typically a@MainActortype touched from a background task. -
Async misuse —
'async' call in a function that does not support concurrency. The call site needs an async context, not a semaphore.
Each shape wants a different fix. Reading the first error tells you which shape you are in; reading the twentieth tells you nothing.
Triage checklist
1. Open the issue navigator (⌘5), not the code.
It groups by file and orders by build phase. The first error in the first file is almost always the root; the rest is cascade.
2. Read the error line and its indented notes.
In Swift 6 the note carries the real information: note: capture of 'state' by closure requires explicit isolation, note: consider making 'Foo' conform to 'Sendable', note: annotate with '@MainActor'. The error names the symptom; the note names the fix.
3. Classify before you fix.
One question: is this about where the code runs (isolation) or what it carries (Sendable)? Isolation fixes are annotations — @MainActor, nonisolated, sending. Sendable fixes are type surgery: value semantics, immutable stored properties, or moving the type inside the actor.
4. Clean build only when the list looks impossible.
Product → Clean Build Folder (⇧⌘K) then ⌘B. Stale module interfaces emit diagnostics for code you already deleted. Do this after the first round of real fixes, or you throw away the cache that shows what changed.
5. Verify with a focused build.
Build the single scheme that failed. If the same error returns at a different line, you fixed a cascade rather than a cause.
Reading the diagnostic without leaving the IDE
The friction is not Swift — it is that the diagnostic is rendered text you cannot cleanly select. Dragging across a twenty-line note picks up line numbers and breaks at indent boundaries; pasting into a translator scrambles the nesting, and you lose which note belongs to which error.
So stop moving the text. Select the region on screen and read it in place: capture the rectangle containing the error and its notes, recognize locally, render the result beside the diagnostic. Two properties make this survivable during a build loop:
- Nothing touches the clipboard. A clipboard overwritten with error text is how the fragment you were about to paste disappears.
- Local recognition, text-only egress. The image stays in memory; only the recognized string goes out for translation. On an NDA'd codebase this is the difference between reviewable and not.
Cheap wins before adopting anything: ⌘5 for the navigator, ⇧⌘K for clean build, ⌥-click a symbol for the documentation popover instead of opening a browser.
What this does not solve
- Failures that only reproduce on a device (simulator logs differ)
- Linker errors naming a symbol you never wrote — usually a transitive dependency
- Toolchain mismatch after an Xcode update: that needs
xcode-selectand the toolchain list, not reading skill - Diagnostics in a non-English locale, where the note structure differs
Links
16:9 walkthrough (Ep3, Xcode errors):
https://www.youtube.com/watch?v=sU03dDj9080
Xcode error flow, direct download page:
https://www.zipp-mac.com/solutions/xcode-swift-build-error-japanese/?utm_source=devto&utm_medium=article&utm_campaign=xcode16_concurrency
Distribution page (BOOTH):
https://zipp-mac.booth.pm/items/9082185
Top comments (0)