Home > Articles > Mobile Application Development & Programming

This chapter is from the book

Recipe: UIManagedDocument and Core Data

The UIManagedDocument class allows you to work with ubiquitous Core Data stores with iCloud. This class integrates data with the cloud. It offers all the built-in services you need for a Core Data–compliant managed model object and extends those services to ubiquitous files. At the time this chapter was written, support for this new class was just coming online. Keep that preliminary nature in mind as you read this section as details have likely changed.

Although the class is derived from UIDocument, there are basic differences between the way you use UIManagedDocument and UIDocument:

  • You may want to use the data container, and not Documents—That’s because the default Core Data store created by UIManagedDocument (i.e., not a standard SQLite store) contains a rather complex file structure. Moving out of the Documents folder allows you to handle those items as a single unit rather than expose the individual files to the end user in his or her iCloud preferences.
  • Listen for persistent store content changes—In addition to document state changes, your application needs to listen for persistent store updates. NSPersistentStoreDidImportUbiquitousContentChangesNotification indicates your application should merge iCloud changes into your managed context.
  • Merge external changes—Use a method similar to the one discussed in this recipe to integrate inserted, modified, or deleted objects into your data store.
  • Do not save your changes—Unlike UIDocument, where you can save both early and often, you only save a UIManagedDocument on creation—and you do so there in a rather tricky fashion, as you’ll see in the steps that follow.

Keep these differences in mind as you move forward to the following how-to write-up.

Remove All Context Saves

The first iCloud refactoring step involves removing all context saves from your application. Any time you see code like this,

NSError *error = nil;
if (![context save:&error])
    NSLog(@"Error: %@", [error localizedDescription]);

go ahead and comment it out. UIManagedDocument handles all context saves for you.

Establish Your Identifiers and URLs

Your application should establish two key identifiers that you will use throughout your managed document implementation. They include

  • A real-world ready name that your new file will use when it is saved to the sandbox (e.g., “ToDo”)
  • A unique name to use when saving the managed store to the cloud. Use a standard reverse-domain style for this private identifier, according to Apple standards.

Here’s how those identifiers might look in your source file:

#define SharedFileName   @"ToDo"
#define PrivateName     @"com.sadun.CloudLearning.storage"

Next, create two key URLs that build on these identifiers. The first is a local URL. It points to the sandbox and uses the real-world file name. The second is a cloud URL. It points to the data storage area of your ubiquitous container and uses the private reverse domain identifier.

NSURL *localURL = [CloudHelper localFileURL:SharedFileName];
NSURL *cloudURL = [CloudHelper ubiquityDataFileURL:PrivateName];

The local and cloud URLs work as a pair. The local item points to a sandbox shell. The managed document links that shell to the persistent store, which is located in the ubiquitous container at the cloud URL.

Establish the Document

Create a new managed document object by allocating it and pointing it to the sandbox URL. Your UIManagedDocument instance should always point to the sandbox item and not to the ubiquitous persistent store. Here’s how you can set up the object with the local URL:

// Establish the document by pointing to the local sandbox
document = [[UIManagedDocument alloc] initWithFileURL:localURL];

The document’s persistent store options declare the content name and include a pointer to the cloud URL. They also should establish that the store migrates its data automatically and use an inferred mapping model. Set the options like this:

// Set the persistent store options to point to the cloud
NSDictionary *options = [NSDictionary dictionaryWithObjectsAndKeys:
    PrivateName, NSPersistentStoreUbiquitousContentNameKey,
    cloudURL, NSPersistentStoreUbiquitousContentURLKey,
    [NSNumber numberWithBool:YES],
        NSMigratePersistentStoresAutomaticallyOption,
    [NSNumber numberWithBool:YES],
        NSInferMappingModelAutomaticallyOption,
    nil];
document.persistentStoreOptions = options;

Once you’re done setting the store options, you’re ready to read in the file if it exists or create it. Allocating a document and setting its URL does not open the file; it merely creates an instance of the class. You must use that instance to save or open the file.

Opening the Document

Here’s a basic rule of thumb: When the sandbox item exists, you can assume that the ubiquitous store it links to exists as well. The converse is not true. A ubiquitous store created on another device might not have a local shell component. In that case, you can create one.

Test for the sandbox file using NSFileManager and the local URL. If the file exists, open it and perform a first fetch on its data. You’re then ready to start operating as you normally do.

if ([helper isLocal:SharedFileName])

{
    NSLog(@"Attempting to open existing file");
    [document openWithCompletionHandler:^(BOOL success){
        if (!success) {NSLog(@"Error opening file"); return;}
        NSLog(@"File opened");
        [self performFetch];;
    }];
}

When the file is not available, create it in the sandbox. Do this regardless of whether the ubiquitous file exists or not. If it exists, the sandbox shell links to it. If it does not, both “files” are created at the same time.

This snippet creates the file, closes it, and then opens it up again. This is probably overkill, but I found that it works consistently in my testing and, when skipping these steps, it does not. Your mileage is sure to vary, especially after the beta period for this new release is over and this book goes live. When the ubiquitous portion does not yet exist, UIManagedDocument automatically creates the persistent store component in the location you specified in its options. In the end, the document exists in two places on each device: the store in the cloud and the wrapper in the sandbox.

{

    NSLog(@"Creating file.");
    // 1. save it out, 2. close it, 3. read it back in.
    // You probably can get away with doing less
    [document saveToURL:localURL
       forSaveOperation:UIDocumentSaveForCreating
       completionHandler:^(BOOL success){
           if (!success) { NSLog(@"Error creating file"); return; }
           NSLog(@"File created");
           [document closeWithCompletionHandler:^(BOOL success){
               NSLog(@"Closed new file: %@", success ?
                   @"Success" : @"Failure");
               [document openWithCompletionHandler:^(BOOL success){
                    if (!success) {
                        NSLog(@"Error opening file for reading.");
                           return;}
                        NSLog(@"File opened for reading.");
                        [self performFetch];;
           }];

         }];
    }];
}

Start Observing

Edits on each device are propagated out via iCloud updates. You need to listen for persistent store updates to respond to these changes, so subscribe in your setup to the following notification:

[[NSNotificationCenter defaultCenter]addObserver:self
    selector:@selector(documentContentsDidUpdate:)
    name:NSPersistentStoreDidImportUbiquitousContentChangesNotification
    object:nil];

Implement a cloud-updated method (the name is arbitrary, although documentContentsDidUpdate: is typical) to match the notification selector. The following method relays the notification data to an asynchronous method that merges the update with the current store:

- (void) documentContentsDidUpdate: (NSNotification *) notification
{
  NSDictionary* userInfo = [notification userInfo];
  [context performBlock:^{
    [self mergeiCloudChanges:userInfo forContext:context];}];
}

From here, it’s up to the mergeiCloudChanges:forContext: method, which you can read through in Recipe 18-4, to manage those merges. This code is again adapted from Apple sample code. It iterates through the updated, refreshed, and invalidated objects and applies those changes to the local managed context.

The merging rounds out the updates made to the standard Core Data application. All other elements of your app can remain as they were prior to iCloud integration.

Recipe 18-4 Ubiquitous Core Data

#pragma mark Initialize the Core Data Stores

- (void) initCoreData
{
    NSURL *localURL = [CloudHelper localFileURL:SharedFileName];
    NSURL *cloudURL = [CloudHelper ubiquityDataFileURL:PrivateName];

    // Create the document pointing to the local sandbox
    document = [[UIManagedDocument alloc] initWithFileURL:localURL];

    // Set the persistent store options to point to the cloud
    NSDictionary *options = [NSDictionary dictionaryWithObjectsAndKeys:
        PrivateName,
            NSPersistentStoreUbiquitousContentNameKey,
        cloudURL,
            NSPersistentStoreUbiquitousContentURLKey,
        [NSNumber numberWithBool:YES],
            NSMigratePersistentStoresAutomaticallyOption,
        [NSNumber numberWithBool:YES],
            NSInferMappingModelAutomaticallyOption,
  nil];
    document.persistentStoreOptions = options;
    context = document.managedObjectContext;

    // Register as presenter
    coordinator = [[NSFileCoordinator alloc]
        initWithFilePresenter:document];
    [NSFileCoordinator addFilePresenter:document];

    // Check at the local sandbox
    if ([helper isLocal:SharedFileName])
    {
      NSLog(@"Attempting to open existing file");
        [document openWithCompletionHandler:^(BOOL success){
            if (!success) {NSLog(@"Error opening file"); return;}
            NSLog(@"File opened");

            [self performFetch];;
        }];
  }
  else
  {
        NSLog(@"Creating file.");
        // 1. save it out, 2. close it, 3. read it back in.
        // You probably can get away with doing less
        [document saveToURL:localURL
           forSaveOperation:UIDocumentSaveForCreating
         completionHandler:^(BOOL success){
             if (!success) { NSLog(@"Error creating file"); return; }
             NSLog(@"File created");
            [document closeWithCompletionHandler:^(BOOL success){
                NSLog(@"Closed new file: %@", success ?
                    @"Success" : @"Failure");
            [document openWithCompletionHandler:^(BOOL success){
                   if (!success) {
                      NSLog(@"Error opening file for reading.");
                      return;}
                   NSLog(@"File opened for reading.");

                   [self performFetch];;
         }];
       }];
     }];
  }

  // Register to be notified of changes to the persistent store
  [[NSNotificationCenter defaultCenter]addObserver:self
        selector:@selector(documentStateChanged:)
        name: NSPersistentStoreDidImportUbiquitousContentChangesNotification
        object:nil];
}

#pragma mark Courtesy of Apple. Thank you Apple
// Merge the iCloud changes into the managed context
- (void)mergeiCloudChanges: (NSDictionary*)userInfo
    forContext: (NSManagedObjectContext*)managedObjectContext
{
  @autoreleasepool

  {
        NSMutableDictionary *localUserInfo =
          [NSMutableDictionary dictionary];

        // Handle the invalidations
        NSSet* allInvalidations =
            [userInfo objectForKey:NSInvalidatedAllObjectsKey];
        NSString* materializeKeys[] = { NSDeletedObjectsKey,
               NSInsertedObjectsKey };
        if (nil == allInvalidations)
        {
            int c = (sizeof(materializeKeys) / sizeof(NSString*));
            for (int i = 0; i < c; i++)
            {
        NSSet* set = [userInfo objectForKey:materializeKeys[i]];
        if ([set count] > 0)
        {
          NSMutableSet* objectSet = [NSMutableSet set];
          for (NSManagedObjectID* moid in set)
              [objectSet addObject:[managedObjectContext
                  objectWithID:moid]];
         [localUserInfo setObject:objectSet
              forKey:materializeKeys[i]];
        }
      }
            // Handle the updated and refreshed Items
            NSString* noMaterializeKeys[] = { NSUpdatedObjectsKey,
                NSRefreshedObjectsKey, NSInvalidatedObjectsKey };
            c = (sizeof(noMaterializeKeys) / sizeof(NSString*));

            for (int i = 0; i < 2; i++)
            {
                NSSet* set = [userInfo objectForKey:noMaterializeKeys[i]];
                if ([set count] > 0)
                {
                    NSMutableSet* objectSet = [NSMutableSet set];
                    for (NSManagedObjectID* moid in set)
                    {
                         NSManagedObject* realObj =
                            [managedObjectContext
                                objectRegisteredForID:moid];
                         if (realObj)
                            [objectSet addObject:realObj];
          }
          [localUserInfo setObject:objectSet
              forKey:noMaterializeKeys[i]];
        }
      }
      // Fake a save to merge the changes
      NSNotification *fakeSave = [NSNotification
        notificationWithName:
            NSManagedObjectContextDidSaveNotification
        object:self userInfo:localUserInfo];
      [managedObjectContext
          mergeChangesFromContextDidSaveNotification:fakeSave];
    }
    else
      [localUserInfo setObject:allInvalidations
          forKey:NSInvalidatedAllObjectsKey];

    [managedObjectContext processPendingChanges];
    [self performSelectorOnMainThread:@selector(performFetch)
      withObject:nil waitUntilDone:NO];
  }
}

// When notified about a cloud update, start merging changes
- (void) documentContentsDidUpdate: (NSNotification *) notification
{
  NSLog(@"Cloud has been updated.");
  NSDictionary* userInfo = [notification userInfo];
  [context performBlock:^{
      [self mergeiCloudChanges:userInfo forContext:context];}];
}

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020