I picked up SwiftData last year for my app, & it’s been an excruciatingly painful experience. Cloud syncing doesn’t always work, duplicate entries, etc.
Things didn’t really improve this year, although some internal things did, because some bugs have been cleaned up.
But… I just feel lost. I need the foundation of the app to be working, so I can dive into other APIs (Widgets, shortcuts, etc), but it’s been an uphill battle.
Okay, can any skilled devs guide me a little?
Is it possible to use #SwiftData’s non-CloudKit stuff (@Unique), etc. with the new custom (bring your own back-end) stuff?
What about CKSyncEngine? I *really* don’t want to roll my own server stack, but if push comes to shove, I’m doing it.
(If none of that is possible, I may just use Bodega W/ a custom server stack). Thoughts?
Thinking if I should just move away from NSPersistentCloudKitContainer and roll my own syncing with CKSyncEngine instead. Then I'd at least have full control over what's going on.
NSPersistentCloudKitContainer's convenience I was hoping for was the only reason why I moved away from GRDB to CoreData in the first place. I cannot accept that I did all that effort for nothing 
#CloudKit
#CloudKit is driving me crazy… I just can't make syncing shared records work reliably on two devices. Every once in a while something breaks randomly.
My most recent problem is, that I can see notifications coming in, but nothing is getting synced due to the hundreds of errors „Deferring additional work. There is still an active request.“ and „ABC request was cancelled because there is already a pending request of type XYZ“
2/2 In the past I've tackled a similar need as shown in this screenshot: I synced everything, then filtered what was shown per device type.
If I were to use that approach, I could change the “Don't sync" button to “This device”, sync a UUID, filter with that and call it a day.
But I'd really prefer to offer the ability not to send some Objects to the cloud AT ALL!
is not coming up with an idea on how to do so w/ current model, though.
Suggestions? 
Bored on a Saturday? Help me figure out how to conceptually tackle a #coding problem! 
I'm building a #SwiftUI app with #SwiftData persistence and #CloudKit #sync.
Model is pretty simple, two classes – let's call them Object and Group – with a many-to-many relationship.
It would make sense for the User to be able to decide that some Objects are only available on the current device (so, NO sync!), others on all iPhones, etc.
See screenshots for the desired behavior.
1/2
I have activated CloudKit in my SwiftData app. This was really so easy! But: already stored local data is not synced. So you should activate CloudKit before deploying to the App Store the first time! Shoutout to @StewartLynch for his great YouTube Tutorial, you are invited for a large Ko-fi 
#CloudKit #SwiftData #AppStore #swiftui https://youtu.be/H5zvrFJMhuE?si=Xs-uxpurkWqWodDZ
Finally got #SwiftData and #CloudKit to play nice but I couldn't figure out why I wasn't seeing anything in the dashboard. I was ready to throw my computer out the window until I realized I was logged in with my personal Apple ID and not my developer account 
I’m getting another surge of email about iCloud/CloudKit sync errors, specifically Error 500, unspecified internal server error.
This seems to happen every year around this time, except this year it already happened back in August.
Let’s hope this is a brief hiccup.
I’m on Mastodon for two things.
I build things on Apple platforms. I make @tact. I read (a lot) and post (a little) about related technologies: #Swift, #SwiftUI, #Combine, #CloudKit, #CoreData, #Xcode, #concurrency, as well as product design.
I support Ukraine. I follow Ukrainians and friends of 
. Please donate to until 
is gone: https://u24.gov.ua or any other respected charity. My Twitter is mostly about Ukraine - https://twitter.com/jaanus
I’m continuing to get several emails a day about #Cloudkit sync failing in my app, and now the 1-star reviews are starting to appear. No errors in logs or CloudKit console.
Is anyone else seeing a rise in CloudKit failures?
For CloudKit subscriptions (CKQuerySubscription), If a single user has several devices, is the subscriptionID supposed to be unique for each device?
Or can I just use an ID of "favorites" across all devices?
I'm guessing it needs to be unique?
https://developer.apple.com/documentation/cloudkit/ckquerysubscription/3003600-init
@mergesort @sindresorhus well if you ever change your mind, remember that we’ve got a #cloudkit channel in slack…
I’m on Mastodon for two things.
I build things on Apple platforms. I make @tact. I read (a lot) and post (a little) about related technologies: #Swift, #SwiftUI, #Combine, #CloudKit, #CoreData, #Xcode, as well as product design.
I support Ukraine. I follow Ukrainians and friends of . Please donate to until is gone: https://ukraineaidops.org or any other charity. My Twitter is mostly about Ukraine - https://twitter.com/jaanus
I’m here for three things.
- Supporting Ukraine, hearing directly from Ukrainians. Hence my #NAFO profile header. Please donate to until is gone: https://ukraineaidops.org or any other charity.
- Sharing and learning about development on #Apple platforms. #Swift, #SwiftUI, #CoreData, #CloudKit etc. I have background in both UX and engineering. I work as freelance developer and have my own project https://justtact.com
- Our little cute 
cesspit. Might post in Estonian sometimes.
