Anton Gubarenko iOS Articles & Videos

I joined most of the sessions and, as usual, prepared a transcript: grouped, polished, and enriched with time codes. And there are plenty of sessions still to go! So I decided to start a series, probably a long one, with gathered Q&A from those Labs.

As usual, the goal is simple: make the questions easier to scan, easier to revisit, and easier to connect with real app development problems.

Many developers struggle to get stable results from AI tool interactions. This can even build a strong opinion that such tools are unreliable: “We don’t need them. I’m used to doing everything on my own.” Fair enough.

But just like Xcode, the Simulator, or any other development tool/service, AI tools need to be tuned and adapted. Even cars have seat, steering wheel, and mirror adjustments.

The article explains that @Environment(.scenePhase) works reliably only in a pure SwiftUI app with SwiftUI lifecycle. When a SwiftUI view is hosted inside UIKit via UIHostingController, scenePhase may not behave as expected because the view does not participate in SwiftUI's scene model. The recommended alternatives are observing UIApplication notifications (didBecomeActiveNotification, willResignActiveNotification) for app wide state, or UIScene notifications (didActivateNotification, willDeactivateNotification, didEnterBackgroundNotification, willEnterForegroundNotification) for scene level behavior closer to scenePhase semantics.

This is a transcript of a live Q&A session with Apple engineers answering specific questions about Swift Concurrency. Topics include the difference between Task { @MainActor in } and MainActor.run, the meaning of nonisolated and nonisolated(nonsending), using @concurrent for offloading work, task cancellation best practices, actor limits, the new withDeadline proposal, migration from Swift 5 to Swift 6 concurrency, and testing async code.