Databases
StackOverflow2013
Postsdbo
POiCloud + Core Data - When to know to seed the iCloud core data store?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POiCloud + Core Data - When to know to seed the iCloud core data store?
    primarykey
    data
    text
    <p>I am working to implement iCloud core data sync in my iPhone app. I am working on the user workflow, and the problem that I am encountering is trying to figure out when my app should "seed" the data to iCloud. This can happen under two use cases: (1) When the app is first installed and I want to seed with some pre-loaded data, or (2) if a pre-existing customer downloads the iCloud update, and their existing data should be uploaded to the iCloud. In each of these cases, I will have a "seed store" in the application which I will read from and upload the data to iCloud.</p> <p>The problem is, how do I know if the data has already been seeded? One option is to <em>delete the seed store</em> from the device once seeding is completed, so that the next time the app launches, it will know that it does not need to seed again.</p> <p>But, what if the store was already seeded from a different device? Is there some sort of flag I can check in iCloud which will tell me that the data should not be seeded? Or, am I forced to <em>always</em> seed the data when the local seed store is extant, and then de-dupe? That will cause problems because the initial seed data (from the app's initial launch after installation) is user-deletable, and so if they (1) install the app on their iPhone, and then delete the default data set, and then (2) install the app on their iPad, then the default data set will be re-uploaded <em>again</em>.</p> <p>Another option that just occurred to me is that when the user installs the app, or turns on iCloud, I could ask the user: Have you already uploaded data? Do you want to replace any data in iCloud with the local data? And if they say yes, then it will nuke iCloud's data store and then re-seed with local data. The problem with this, however, is that it creates the possibility of user error—and this is something that I don't want users to screw up.</p> <p>Any thoughts?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJason
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POiCloud + Core Data - When to know to seed the iCloud core data store?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POiCloud + Core Data - When to know to seed the iCloud core data store?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POiCloud + Core Data - When to know to seed the iCloud core data store?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODon't understand why that .NET guy closed this question as off topic. Asking user seem to be the only reliable way which is sad. Unfortunately iCloud is still kind of a black box with no proper handles. I encourage you to read this thread https://devforums.apple.com/thread/126670?tstart=0 on Apple dev forum (must be registered developer to access it)
      singulars
      1. POiCloud + Core Data - When to know to seed the iCloud core data store?
      1. USKostiantyn Sokolinskyi
    2. COI agree. Why was this closed? I am looking for other programmers' advice on how to resolve this problem.
      singulars
      1. POiCloud + Core Data - When to know to seed the iCloud core data store?
      1. USJason
    3. COThere's a similar question that's already answered here: http://stackoverflow.com/questions/9097541/icloud-coredata-how-to-avoid-pre-filled-data-duplication
      singulars
      1. POiCloud + Core Data - When to know to seed the iCloud core data store?
      1. USadib
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload