Using Core Data, iCloud and CloudKit for syncing and backup and how it works together

by

It’s like this:

  • Core Data on its own, is completely local and does not automatically work with any of Apple’s cloud services.
  • Core Data with iCloud enabled turns on syncing via iCloud. Any changes you save in Core Data are propagated to the cloud, and any changes made in the cloud are automatically downloaded. The data is stored both in iCloud and in a local persistent store file, so it’s available even when the device is offline. You don’t have to write any cloud-specific code, you just need to add listening for incoming changes (which is a lot like changes made on a different managed object context).
  • CloudKit is not related to Core Data. It’s not a sync system, it’s a transfer system. Meaning that any time you want to read/write cloud data, you need to make explicit CloudKit API calls to do so. Nothing happens automatically. CloudKit does not store data on the device, so the data is not available if the device is offline. CloudKit also adds some features not available to Core Data with iCloud– like public shared data and the ability to download only part of the data set instead of the whole thing.

If you wanted to use CloudKit with Core Data, you’d have to write your own custom code to translate between managed objects and CloudKit records. It’s not impossible, but it’s more code to write. It might be more reliable but it’s too soon to say for sure.

I wrote a blog post describing CloudKit from the perspective of someone who’s used Core Data and iCloud in the past.

Update, June 2016: As of the most recent documentation for NSPersistentStoreCoordinator, everything related to Core Data with iCloud is marked as deprecated. As a result it should probably be avoided for new development.

More Related Contents:

  1. Swift Send Data to a ViewController from a ViewController [duplicate]
  2. Any way to pre populate core data?
  3. Core Data: Quickest way to delete all instances of an entity
  4. Adding Core Data to existing iPhone project
  5. How to save Array to CoreData?
  6. Sqlite File Location Core Data
  7. Core Data and iOS 7: Different behavior of persistent store
  8. Check if property is set in Core Data?
  9. Core Data background context best practice
  10. NSPersistentContainer concurrency for saving to core data
  11. Xcode is looking for core data entity names with dot; not compiling
  12. How to add unique constraints for some fields in Core Data
  13. How to create managedObjectContext using Swift 3 in Xcode 8?
  14. NSFetchedResultsController v.s. UILocalizedIndexedCollation
  15. Swift 3 Core Data Delete Object
  16. When should I use the various storage mechanisms in iOS?
  17. iPhone Core Data “Automatic Lightweight Migration”
  18. How do you update a CoreData entry that has already been saved in Swift?
  19. How to print Core Data debug values?
  20. Core Data in Swift: Only saving last object in a for loop
  21. Correct implementation of parent/child NSManagedObjectContext
  22. Storing UIColor object in Core Data
  23. How do I delete all objects from my persistent store in Core Data?
  24. How to get managedObjectContext for viewController other than getting it from appDelegate?
  25. How to get URL for a PHAsset? [duplicate]
  26. CKQuery from private zone returns only first 100 CKRecords from in CloudKit
  27. Accessing Core Data Stack in MVVM application
  28. How to properly group a list fetched from CoreData by date?
  29. Implementing Fast and Efficient Core Data Import on iOS 5
  30. How to disable no inverse relationship warning for CoreData in Xcode 4.2?

Leave a Comment