Notifications crashing with concurrency errors? Replace unsafe π‘›π‘œπ‘‘π‘–π‘“π‘¦() calls with π˜”π˜’π˜ͺπ˜―π˜ˆπ˜€π˜΅π˜°π˜³π˜”π˜¦π˜΄π˜΄π˜’π˜¨π˜¦ and π˜ˆπ˜΄π˜Ίπ˜―π˜€π˜”π˜¦π˜΄π˜΄π˜’π˜¨π˜¦. Thread-safe, modern, and built for async/await.

πŸ”— https://www.avanderlee.com/concurrency/mainactormessage-asyncmessage-concurrency-safe-notifications/ by Antoine van der Lee (@swiftlee)

#Concurrency #SwiftConcurrency #iOS

MainActorMessage & AsyncMessage: Concurrency-safe notifications

Dive into notifications and Swift concurrency. Discover the updated notification API that ensures thread safety.

SwiftLee