Looks like the CloudKit sync issue in *OS 26.4 is real (I can repro with all of my apps), and has the very distinct potential to lead to catastrophic data loss and/or sync conflicts across effectively all apps. Apps only receive changes from the cloud after being quit and relaunched.

If Apple hasn't pulled 26.4 already, it should do so immediately until there's a fixed build

https://mastodon.social/@lukaskubanek/116299581006179836

@stroughtonsmith I tend to disagree. Error handling is mandatory for an app using CloudKit and I can’t see how it could lead to “catastrophic data loss”. Remote notifications have never been reliable. This is a best effort service?
@slizeray @stroughtonsmith I also don’t see how it can lead to data loss because apps should handle duplication / conflict resolution when using CloudKit. But the current issue leads to bad user experience because apps just don’t have any idea of it and people will see their apps out of sync.
@alpennec @stroughtonsmith What is difficult to understand is that Apple explains to developers how to test their applications but that they themselves are unable to avoid catastrophic regression bugs.
I have already experienced catastrophic regression bugs with HealthKit and MapKit. It was eventually fixed with MapKit, but not with HealthKit…