Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4584800
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 21, 20262026-05-21T21:24:18+00:00 2026-05-21T21:24:18+00:00

I’ve got an app design question that I’m hoping someone can help with. Let’s

  • 0

I’ve got an app design question that I’m hoping someone can help with.

Let’s take a very simple setup: Core Data app for displaying news items from a server.

  • Main thread / UI has a managed object context that’s used by all the view controllers to display the data.

  • An NSOperation runs in the background checking the server, with it’s own context, on the same persistent store.

I want to merge the changes in the background context so I use NSManagedObjectContextObjectsDidChangeNotification.

According to the Apple docs:

Several system frameworks use Core Data internally. If you register to receive these notifications from all contexts (by passing nil as the object parameter to an addObserver… method), then you may receive unexpected notifications that are difficult to handle.

So, I want to filter my notifications merged in the main thread MOC to just those changes coming from the background operation MOC.

What’s the cleanest way to get/maintain a reference to the background operation MOC so that I have something to plug into the addObserver method and the notifications are properly filtered? I can think of a lot of ways that involve a lot of coupling but they all seem like a hack.

Any suggestions or ideas? How are others handling this?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-21T21:24:19+00:00Added an answer on May 21, 2026 at 9:24 pm

    Here’s how it works in my app:

    // should be executed on a background thread
    - (void)saveWorkerContext {
        if ([_workerContext hasChanges]) {
            NSNotificationCenter *nc = [NSNotificationCenter defaultCenter];    
            [nc addObserver:self selector:@selector(workerContextDidSave:)
                       name:NSManagedObjectContextDidSaveNotification object:_workerContext];
    
            NSError *error;
            if (![_workerContext save:&error]) {
                NSAssert(NO, @"Error on save: %@", error);
            }
    
            [nc removeObserver:self name:NSManagedObjectContextDidSaveNotification object:_workerContext];
        }
    }
    
    - (void)workerContextDidSave:(NSNotification *)notification {
        if (_mainContext) {
            [_mainContext performSelectorOnMainThread:@selector(mergeChangesFromContextDidSaveNotification:) 
                                           withObject:notification waitUntilDone:NO];
        }
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.