Latest 0.6
Homepage https://github.com/nofelmahmood/Seam
License MIT
Platforms ios 8.3, osx 10.10
Frameworks CloudKit
Authors

Seam

“Simplicity is the ultimate sophistication.”

– Leonardo da Vinci

Seam is a framework built to bridge gaps between CoreData and CloudKit. It almost handles all the CloudKit hassle. All you have to do is use it as a store type for your CoreData store. Local caching and sync is taken care of. It builds and exposes different features to facilitate and give control to the developer where it is demanded and required.

CoreData to CloudKit

Attributes

CoreData CloudKit
NSDate Date/Time
NSData Bytes
NSString String
Integer16 Int(64)
Integer32 Int(64)
Integer64 Int(64)
Decimal Double
Float Double
Boolean Int(64)
NSManagedObject Reference

In the table above : Integer16, Integer32, Integer64, Decimal, Float and Boolean are referring to the instance of NSNumber used to represent them in CoreData Models. NSManagedObject refers to a to-one relationship in a CoreData Model.

Relationships

CoreData Relationship Translation on CloudKit
To – one To one relationships are translated as CKReferences on the CloudKit Servers.
To – many To many relationships are not explicitly created. Seam only creates and manages to-one relationships on the CloudKit Servers.
Example -> If an Employee has a to-one relationship to Department and Department has a to-many relationship to Employee than Seam will only create the former on the CloudKit Servers. It will fullfil the later by using the to-one relationship. If all employees of a department are accessed Seam will fulfil it by fetching all the employees that belong to that particular department.

Note : You must create inverse relationships in your app’s CoreData Model or Seam wouldn’t be able to translate CoreData Models in to CloudKit Records. Unexpected errors and curroption of data can possibly occur.

Sync

Seam keeps the CoreData store in sync with the CloudKit Servers. It let’s you know when the sync operation starts and finishes by throwing the following two notifications.

  • SMStoreDidStartSyncOperationNotification
  • SMStoreDidFinishSyncOperationNotification

Conflict Resolution Policies

In case of any sync conflicts, Seam exposes 4 conflict resolution policies.

  • ClientTellsWhichWins

This policy requires you to set syncConflictResolutionBlock block of SMStore. You get both versions of the record as arguments. You do whatever changes you want on the second argument and return it.

  • ServerRecordWins

This is the default. It considers the server record as the true record.

  • ClientRecordWins

This considers the client record as the true record.

  • KeepBoth

This saves both versions of the record.

How to use

  • Declare a SMStore type property in the class where your CoreData stack resides.
    var smStore: SMStore?
  • Add a store type of SeamStoreType to your app’s NSPersistentStoreCoordinator and assign it to the property created in the previous step.
    do 
    {
    self.smStore = try coordinator.addPersistentStoreWithType(SeamStoreType, configuration: nil, URL: url, options: nil) as? SMStore
    }
  • Enable Push Notifications for your app.
    Seam
  • Implement didReceiveRemoteNotification Method in your AppDelegate and call handlePush on the instance of SMStore created earlier.
    func application(application: UIApplication, didReceiveRemoteNotification userInfo: [NSObject : AnyObject]) 
    {
    self.smStore?.handlePush(userInfo: userInfo)
    }
  • Enjoy

Options

  • SMStoreSyncConflictResolutionPolicyOption

Use SMSyncConflictResolutionPolicy enum to use as a value for this option to specify the desired conflict resolution policy when adding SeamStoreType to your app’s NSPersistentStoreCoordinator.

Requirements

Xcode 7

Swift 2.0

Support

What it does support

Seam supports only user’s CloudKit Private Database at this time. It creates and uses a custom zone to store data and fetch changes from the server.

What it does not support

CloudKit Public Database and here are the two reasons why, straight from the docs.

  1. The disadvantage of using the default zone for storing records is that it does not have any special capabilities. You cannot save a group of records to iCloud atomically in the default zone. Similarly, you cannot use a CKFetchRecordChangesOperation object on records in the default zone.

  2. You cannot create custom zones in a public database.

Getting Started

Download the demo project. Run it and see the magic as it happens.

Installation

CocoaPods is the recommended way of adding Seam to your project.

Add this 'Seam', '~> 0.6' to your pod file.

Credits

Seam was created by Nofel Mahmood

Contact

Follow Nofel Mahmood on Twitter and GitHub or email him at [email protected]

License

Seam is available under the MIT license. See the LICENSE file for more info.

Latest podspec

{
    "name": "Seam",
    "version": "0.6",
    "license": {
        "type": "MIT"
    },
    "homepage": "https://github.com/nofelmahmood/Seam",
    "authors": {
        "Nofel Mahmood": "[email protected]"
    },
    "social_media_url": "https://twitter.com/NofelMahmood",
    "summary": "CloudKit spreading awesomeness through CoreData.",
    "source": {
        "git": "https://github.com/nofelmahmood/Seam.git",
        "tag": "0.6"
    },
    "platforms": {
        "ios": "8.3",
        "osx": "10.10"
    },
    "header_dir": "Seam",
    "source_files": "Seam/**/*.{h,swift}",
    "frameworks": "CloudKit"
}

Pin It on Pinterest

Share This