Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated project #33

Open
wants to merge 2 commits into
base: Improve-Store
Choose a base branch
from

Conversation

oskarirauta
Copy link

  • SMStoreDidStartSyncingNotification now works for those who need it.
  • Updated project for Xcode 7.2
  • Fixed one error and one warning
  • Made iOS example tabular, now it has a new tab Settings which
    explains how to store setting values in CoreData + back them up/sync
    them with CloudKit. I also added a simple mechanism to sync process for
    avoiding multiple records with same identifier, which in this case, is
    a name of setting. Mechanism uses current date/time while saving
    setting the first time. When data is synced and if more than one
    records is found, the oldest one (cloud one) will be the one that is
    stored and others will be removed. It should be pretty simple to use this for other kind of entities too. Or use it to invent your own way to achieve this where needed.
  • I also removed a reference to missing file on workspace.

It works now pretty nicely and also the example runs out of the box. With project specific customizations, I would say, it's ready for production.

Oskari Rauta added 2 commits January 9, 2016 18:15
 - SMStoreDidStartSyncingNotification now works for those who need it.
 - Updated project for Xcode 7.2
 - Fixed one error and one warning
 - Made iOS example tabular, now it has a new tab Settings which
explains how to store setting values in CoreData + back them up/sync
them with CloudKit. I also added a simple mechanism to sync process for
avoiding multiple records with same identifier, which in this case, is
a name of setting. Mechanism uses current date/time while saving
setting the first time. When data is synced and if more than one
records is found, the oldest one (cloud one) will be the one that is
stored and others will be removed.

It should be pretty simple to use this for other kind of entities too.
Removed a duplication notification..
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant