This is still broken on iOS 26.2 😩
Looking at several projects I’ve come across recently, I have serious doubts that a largescale transition to Swift 6 is going to happen.
Many teams are still producing large amounts of legacy code that does not take Swift 6 into consideration at all.
This trend seems to be further reinforced by LLMs (that still often generate singletons) and by engineers who simply want to get the job done.
If I want to use a specific Locale in a SwiftUI preview, it’s easy to just add a Locale to the environment, like this:
.environment(\.locale, .init(identifier: "sv"))
But how I can achieve the same thing in a preview of a UIKit view or view controller?
How can you understand AI's impact on iOS development at scale? This reveals how to train Ollama to analyze 1,000 iOS blogs for insights and patterns.
🔗: https://gioscalzo.com/blog/weekend-ios-ai-blog-analyzer/ by Giordano Scalzo
👋 we share iOS/Swift articles every week in our newsletter
enjoying the content? subscribe. means the world for us
Oh, I enabled the localisation catalog thing for my app today. Not done any translations so far as everything has been too much in flux.
Xcode 26.2 extracted the strings as normal but it also created default comments for all strings based on the context the strings were defined in. Unexpected as the comments are mostly pretty good. Saves me a lot of time to go through them all.
First time in a long time that Xcode has positively surprised me.