Post #3794545

@lkanies@hachyderm.io @ripienaar@devco.social I wouldn't claim to have solved sync, but I found it a lot easier from a mental model perspective to just do last-write-wins with merge when receiving updates from CloudKit, store photos as CKAssets, and not try to do any kind of ordering or sequencing of any changes. One outbound queue for local writes going up to the cloud, one separate inbound queue for processing updates, inbound queue can never trigger anything that would cause something to enter outbound queue, to avoid feedback loops. It does mean users of my app see weirdness like photos for entities arriving before the entity text on a brand new device, but have had zero complaints about "lost updates" since switching to this model. Oh, and I got a *lot* less frustrating outcomes using UIKit rather than SwiftUI. Uglier code, but LLMs seem to have less difficulty with it, more OOTB performance.