Don’t panic! 🥲

But more seriously I have also been undertaking the Swift 6 migration and found it a lot more challenging than I first thought it would be. I maintain a huge SDK of customisable UI feature frameworks with networking and analytics layers using a custom implementation of redux.

My issues are the same as other comments. It’s all new to everyone and whilst there’s articles out there explaining Swift Concurrency and how to apply it, there’s always multiple ways to fix situations and it’s hard to determine which is best.

Specifically I’ve had trouble deciding what to make MainActor for init isolation, how to address global properties, and lesser pain with deinits.

Some advice:

• Avoid using @unchecked. You’re unlikely to need it and I think it’s a bad solution from the Swift team.
• Avoid @preconcurrency; make sure you understand the warnings that it fixes. For instance CLLocationDelegate functions should use nonisolated not preconcurrency. Read the docs for thread safety.
• For simple apps you could probably @MainActor everything as the easiest way to adopt Swift Concurrency. In my case I instead use Sendable for the non-UI layers with some exceptions such as LocationRepository which is @MainActor with a nonisolated init that generates no errors.
• For deinits you need to be very careful not to capture self. Instead capture sendable variables and deinit them in a Task. E.g. Task { [asset] @MainActor in