Yuto
Lukas KubanekLooks like Apple broke #CloudKit sync in OS 26.4. Remote notifications don’t seem to arrive, so no updates unless the app is relaunched. https://developer.apple.com/forums/thread/820550
I somehow assumed Apple would treat the #CloudKit bug as top priority without giving it a second thought, so I actually overlooked the phrasing the DTS engineer used in their post that @iandundas pointed out. Kinda crazy!
Good news! Based on my initial tests on iOS 26.5 beta and reports from others in the community, CloudKit sync seems to be working again.
Jérôme@lukaskubanek @cdfinder @iandundas WTF?!? So, if you don’t file a bug report they will not (or only accidentally) fix it?
NMDoerner@jxrxme @lukaskubanek @iandundas
Well, Apple usually completely ignores my error reports anyway, but this is really a bad joke, Timmy!
Jim Rea@lukaskubanek @iandundas The last radar I ever filed was in 2019 after WWDC. An engineer helped me devise a workaround for an issue, which I much appreciated. His supervisor asked me to file a radar. Reluctantly, I did, and referenced the supervisor. Of course it came back as won’t fix, so a complete waste of my time. I wouldn’t mind the no pay if they actually fixed things. But yeah - do your own damn work.
Georg Tuparev@provuejim @lukaskubanek @iandundas
My stats are not that bad - ca. 30% are taken care of, and in about 5% I am actually contacted personally. But it is a lot of effort to file a Rader as I do, because at least 50% of the cases, I am also trying to submit a complete mini project, that exposes the problem.
Perhaps it heals, that I know few people at Apple too.
@tuparev @provuejim I still file them from time to time but also collect them in a repo (https://github.com/structuredpath/AppleBugReports) so I can quickly check if they’re fixed on newer OS versions. It now takes much less time with AI support and it helps me find workarounds… But yeah, my stats are also pretty bad. It feels like only feedbacks pushed through Apple employees get attention if at all.
Heals 
@lukaskubanek Apple is great at acknowledging "severe" and "immense" issues and then putting them into a drawer never to talk about them again. See the SwiftData background update issues that iOS 18.0 introduced, probably hundrets of devs reported and that is still around in 26.4 :|
/cc @kaioelfke
Amy Worrall@lukaskubanek that’s quite the regression!
@amyworrall Yeah, I honestly don’t understand how this could ship unnoticed. Crazy!
Sam Clemente@lukaskubanek How does one, pray tell, manage to break the backbone of scheduled background tasks and then proceed to *ship it*
@lukaskubanek Craig rolling in his grave (that golf cart that rides around Apple Park) right now
@lukaskubanek Craig coming to break down the door of the infra dev who managed to ship this broken
Stephanie@countablenewt @lukaskubanek Someone vibe coded their changes without a thinking human in the loop.
Ben Haylock 
@lukaskubanek Send up the bat signal for @justkwin ! 🤣
Quinn “The Eskimo!”@zbender @lukaskubanek Yeah, I’m willing to go out on a limb here and say that this is Not Good™.
Fortunately, there’s a couple of top notch DTSers on the case. If you haven’t already done so, please follow Ziqiao’s advice in this post:
https://developer.apple.com/forums/thread/820550?answerId=881814022#881814022
Brendan@TapForms 🇨🇦@justkwin @zbender @lukaskubanek weird. I wrote a new sync engine using CKSyncEngine and it seemed to work sometimes. I was testing last night by making a change on an old Sonoma MBP and I watched my 26.4 Tahoe Mac update. It took about a minute to update though but it did without my intervention. But I have noticed the notifications don't always arrive so I have to manually sync frequently. Maybe it's only an iOS 26.4 issue. I'll do more testing and file feedback.
Daniel ☀
@lukaskubanek Good grief at the quality of software these days!
Ian
Daniel Kasaj@lukaskubanek not "relaunched", brought back to foreground
@danielkasaj I ran some quick tests on two iOS 26.4 devices in the development environment. From what I can tell, a fetch only happens when the app is (a) relaunched or (b) brought back to the foreground after a delay since the last fetch (~40s). Looks like some kind of scheduling issue.
deeje@lukaskubanek arg, I thought maybe I'd done something. it sucks when they break something so fundamental.