Looks like CloudKit won
Anyone with knowledge of CoreData + CloudKit, can help me with weird issue that drives me nuts?
Looks like CloudKit won
Anyone with knowledge of CoreData + CloudKit, can help me with weird issue that drives me nuts?
It's been out for a couple weeks now, but here's my official post introducing Tap Forms Database Pro for macOS and iOS to the Fediverse! Two years in the making, dozens of new features, Apple Silicon support (finally), AI form generation, a new Reports Generator, iCloud sync across different Apple IDs, built-in Template Library, a more modern look and feel, and more!
Check it out at https://apps.apple.com/app/apple-store/id1527890083?pt=13038&ct=Mastodon&mt=8
I am working on trying to create some derived properties in my CoreData model to count the amount of entries for a tag based on entry type. I shared in the image the total count that is working but the subquery that is not working. Any help would be appreciated. #CoreData #iOSDev #BuildInPublic
It's wild that NSPersistentCloudKitContainer, or CloudKit in general for that matter, still does not support unique constraints in 2025. Wonky deduplication code is my biggest issue with sync. This is a feature which nearly every app needs and is so hard to get right. #SwiftUI #Swift #CoreData #iCloud #UIKit
And here is the blog post detailing the changes.
https://smork.info/blog/posts/beer-diary-version-2-1-released/
Has anyone encountered such a problem? Do we really need to worry about it? It seems like some SwiftData internal problem, as there is no way to work around it as there is in #CoreData.
And here is the blog post detailing the changes. It also includes some development background information in case you're interested.
https://smork.info/blog/posts/beer-diary-version-2-0-released/
It is 2025, and there are still people writing #SQL to combine with their #Swift code.
In 1993 NeXT introduced Enterprise Object Framework (EOF) and in 1995 - WebObjects. Since that time my team and I never wrote a single SQL query (exception - testing).
We are complaining about AI, but still write SQL! Folks, this is regression!
—
#CoreData is based on EOF. Very poor and miserable imitation of EOF indeed (also sign of the downfall of the empire).
Many thanks to @seanallen_dev & @bigmountainstudio for helping me update my TestFlight app using CoreData.
I want to support iOS15 for some family iPhones I can’t inspire away. & I think for undo/redo support made #coredata worth it.
I find both your material really inspiring… But sometimes Sean’s video format is harder to use for quick reference. And while Mark's visual book format is great - I would have preferred small working apps to the big several example one.
I do like using Cursor for helping me make debugging scripts a lot. This one parses all the #CoreData sqlite query logs and makes a spreadsheet out of them with their execution time + the fault/action that triggered the query. https://gist.github.com/juanarzola/d1af93e8d677766c9cd57253b24352d8
Does someone know what benefits/effects changing the "Tools Version" of your CoreData-Model has?
If that fails, I’ll switch to #CoreData, as there are much more materials on how to deal with it, not to mention it’s a mature framework. Now it’s time to at last rest before the new week!
#BuildInPublic #IndieDev #iOSDev
All that made me think, maybe #CoreData would be a better choice, but at this point I’m a bit afraid to change everything. On the other hand, it’d be better to do it now than after the official release, I guess.
#Swift #iOSApp #AppDevelopment
I haven't seen anything at WWDC regarding sharing #SwiftData with other users. Did I miss something?
When I looked into it last year I walked away with the impression that it's only possible with #CoreData. But now I'm thinking, since SwiftData is just a wrapper around Core Data, sharing has to be possible somehow.
Not finding anything on the topic. It doesn't help that I've never done it using Core Data. Looks like I should just try it so I understand the problem space.
The holidays have given me a little time to work on my oldest app Bakeshop. It's been in dire condition for a long time, but having a full time engineering job doesn't give me much time.
Version 6 of the app has undergone a significant code transformation in order to make it easier and quicker to release improvements, using all the latest technologies: #SwiftLang #SwiftUI #CoreData #CloudKit
It's in beta on TestFlight now. https://testflight.apple.com/join/I5GiHzLt
Dear #coredata #swiftlang people. It’s been a while since I’ve had to deal with migrations. IIRC back then model versions were mandatory, otherwise the app would crash in production (while doing fine in development). I have a Swift5 app with a #cloudkit backed CoreData db.