fatbobman

A Trip to the Apple Store for Repairs

• 🔥 Hot Reloading SwiftUI Apps
• 🔍 Mobile Testing Strategies
• 🤖 Automate with Swift Subprocess
• 🎢 AsyncCombine

and more...

Qualcomm Acquires Arduino: The Wheel of History Turns

• 🚀 How to Integrate OpenSwiftUI
• 🗓️ Foundation Model Code-Along Q&A
• 🌍 The macOS DNA of Apple Platforms
• 📖 Swift Profile Recorder
• 📁 RichText

and more...

• ✨ Async Result in a Synchronous Function
• 🗓️ Adopting Liquid Glass
• 📖 Swift Configuration
• 📁 AsyncItemProvider

and more...

Fatbobman’s Swift Weekly #0104 is out! Apple is Preparing for System-Level MCP Support

• 💡 Adopting the New Window Controls in iPadOS 26
• 🧐 Benjamin Button Reviews macOS
• 🔍 How I QA iOS Apps
• 🌐 App Store Optimization

and more...

Fatbobman’s Swift Weekly #0103 is out!

Swift 6.2 Is Here

• 🌟 SwiftUI TextField Memory Leak
• 🔍 Processing Swift Actor Usage Advice in Depth
• 📅 Feature Flags in Swift -📖 edge-agent

and more...

Have You Completed Your Liquid Glass Adaptation?

• 🌟 Talk About Observation
• 🔧 The Swift Android Setup
• 🌍 SwiftUI Redraw System In Depth -📖 Swift-Build GitHub Action

and more...

From Open Platform to Controlled Ecosystem: Google Announces Android Developer Verification Policy

• 🚀 MainActor.assumeIsolated
• 🧩 Default Value in String Interpolations
• 📚 OpenAttributeGraph Documentation
• 🔧 macOS Accessibility

and more...

While Swift has offered strict concurrency checking for some time, many of Apple’s official APIs have yet to be fully adapted, and this situation may persist for quite a while. As Swift 6 gradually gains adoption, this problem becomes increasingly prominent: developers want to benefit from the concurrency safety guarantees provided by the Swift compiler, while struggling with how to make their code meet compilation requirements. This article will demonstrate the clever use of MainActor.assumeIsolated in specific scenarios through an implementation case with NSTextAttachmentViewProvider.

For This Journey, and for My Future Self | Fatbobman’s Swift Weekly #0100 is out!

• 🌟 An Analysis of Xcode’s New AI Assistant
• 🎨 Discussion on SwiftData’s ModelActor
• 🔎 Creating Amazing Loading Animations with SF Symbols
• 👁️ SBSObservation

and more...

The Future is Coming: Humanoid Robot Games

• ✨ Corner concentricity on iOS 26
• 🖌️ Vapor on Raspberry Pi
• 🔍 Liquid Glass. Why?
• 📲 Open Intent

and more...

Fatbobman’s Swift Weekly #098 is out! I Almost Lost Patton (My Dog)

• 🌟 TextKit 2
• 🔍 Why LLMs Can’t Really Build Software
• ⏰ Main Menu in SwiftUI
• 📱 NavigationStack + Deep Linking in Large SwiftUI Apps

and more...

Swift’s concurrency model introduces numerous keywords, some of which are similar in naming and purpose, often causing confusion among developers. This article examines several keywords related to cross-isolation domain passing in Swift concurrency: Sendable, @unchecked Sendable, @Sendable, sending, and nonsending, helping you understand their respective roles and use cases.