Marco ArmentRE: https://mastodon.social/@lukaskubanek/116299581006179836
This is a total showstopper for any iOS apps using CloudKit.
Paul Haddad 
@marcoarment soft disagree, CK apps should be architected so that push notifications are a nice to have, not a requirement.
Sören Gade@paul I can also imagine that the reality of many apps is different
Stéphane Lizeray
Lukas Kubanek@slizeray @sense @paul I also agree that apps shouldn’t rely on instant sync and should continue working in “offline” mode. However, with CKSyncEngine, you’re out of luck triggering the sync manually, as you’re handing control over to the system. The promise is that it just works. Until it doesn’t. It’s less of a black box than Core Data but still a black box…
Heals 
@paul keep in mind that a lot of developers use frameworks that wrap CK and those are mostly written to rely on the notifications instead of polling them pushing first - aka “it’s easier said than done if all you did was do as the spec told you”
@heals I 109% accept that it’s an easy mistake for a dev to make on their own app, but if you are shipping a framework for others to use I think you should be familiar enough with the tech to realize this pitfall.
Brendan@TapForms 🇨🇦@paul @marcoarment agree. It's not hard to pull from CloudKit every once in a while or add a Sync Now button. I sync when the app comes to the foreground. Mac and iOS. Plus have a button. And a switch to toggle auto sync. And a sync delay setting.