I Turned on Swift 6 Strict Concurrency. 342 Errors Appeared. Here’s What Actually Mattered.

Last month, our team finally decided to rip off the band-aid.

We opened our project’s Build Settings in Xcode, scrolled down to Strict Concurrency Checking, flipped the dropdown from Minimal to Complete, and hit Cmd + B.

A second of silence. Then:

Build Failed: 342 errors, 118 warnings.

Our senior architect leaned back in his chair, stared at the red wall of text, and sighed:

“Maybe I should just quit programming and open a sourdough bakery.”

Every iOS developer knows this feeling. The jump to Swift 6 feels like you’re suddenly working with a compiler that hates you.

Every protocol, every closure, every singleton, and every background task that compiled cleanly for the past five years is suddenly flagged with cryptic warnings:

• Passing argument of non-Sendable type across actor boundary
• Reference to static property is not concurrency-safe
• Mutation of captured var in concurrently-executing code

It feels overwhelming. It feels like your entire codebase is fundamentally broken.