observeValueForKeyPath is not getting called

Question

I am developing a test app in which I have an NSOperationQueue. I am creating an NSInvocationOperation and observing the "isFinished" property of that operation. Strangely the observeValueForKeyPath is called only sometimes. I am not able to understand the changes i have to make to get it called every time. Please help.

Here is the code i have written :

-(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
    ........//initialization

    queue = [NSOperationQueue new];
    operation=[NSInvocationOperation new];

    operation = [[NSInvocationOperation alloc]initWithTarget:self     selector:@selector(CreateOperationWithContext:) object:context];

    [operation addObserver:self forKeyPath:@"isFinished" options:(NSKeyValueObservingOptionNew | NSKeyValueObservingOptionOld) context:NULL];

    [queue addOperation:operation];

    ..... // launch the view controller
}

-(void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary *)change context:(void *)context
{
    if ([keyPath isEqualToString:@"isFinished"]) {
        NSLog(@"came in");
        [operation removeObserver:self forKeyPath:@"isFinished"];
    }
    else
    {
        [super observeValueForKeyPath:keyPath ofObject:object change:change context:context];
    }
}

How are you verifying when it is and isn't called and is the same check in `CreateOperationWithContext`? — Wain, Aug 12 '13 at 14:12
When you didn't see the notification, are you 100% sure the operation was successfully created, executed, and completed, even though you still didn't see `isFinished` KVN? E.g., if it was unable to resolve `@selector(CreateOperationWithContext:)`, then the operation would never be created in the first place. Or, if `CreateOperationWithContext:` failed to complete (infinite loop, etc.), the operation wouldn't complete, either. Regardless, I'd recommend setting the `completionBlock` for your operation rather than adding an observer for the `isFinished` key. It's cleaner and more reliable. — Rob, Aug 12 '13 at 16:41
Hi Rob and Vain,Thanks for your replies. The function CreateOperationWithContext: gets called every time and is also executed successfully. I am updating the database in the function and i am able to see the update every time. Only the observer is not notified. — user2122350, Aug 13 '13 at 05:35

score 1 · Accepted Answer · edited May 23 '17 at 10:28

The following code works for me. I started from the iOS single view app template. Here is what I had:

@implementation SOAppDelegate
{
    NSOperationQueue* queue;
    NSOperation* operation;
}

- (void)CreateOperationWithContext: (id)foo
{
    NSLog(@"Op ran");
}

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
    queue = [NSOperationQueue new];
    // operation = [NSInvocationOperation new]; // Commented this out because it's redundant with the next line
    operation = [[NSInvocationOperation alloc] initWithTarget:self selector:@selector(CreateOperationWithContext:) object:[NSObject new]];
    [operation addObserver:self forKeyPath:@"isFinished" options:(NSKeyValueObservingOptionNew | NSKeyValueObservingOptionOld) context:NULL];
    [queue addOperation:operation];
    return YES;
}

- (void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary *)change context:(void *)context
{
    if ([keyPath isEqualToString:@"isFinished"])
    {
        NSLog(@"came in");
        [operation removeObserver:self forKeyPath:@"isFinished"];
    }
    else
    {
        [super observeValueForKeyPath:keyPath ofObject:object change:change context:context];
    }
}

// ... rest of empty default app delegate methods here...

@end

In the console, I see:

2013-08-13 08:04:15.150 TestOpKVO[71373:20b] Op ran
2013-08-13 08:04:21.903 TestOpKVO[71373:20b] came in

So something about your implementation of -CreateOperationWithContext: is causing trouble. That said, I still see the KVO notification getting called even if I change the operation to throw an exception.

If I were you I would start from this very basic, working example and then proceed one step at a time to adapt it to your real code, checking at each step to make sure the notification is still working.

A few tips: (that are probably unrelated to the problem you're seeing, but good practices for using KVO)

First, use KVO contexts with your observations. It's safer and more deterministic. See the answer I wrote over here for details.

Second, don't call -removeObserver:forKeyPath: from inside a call of -observeValueForKeyPath: (or -addObserver:... either) for the same keyPath that is being notified for. This has the potential to mess up KVO's internal observer data structures and can cause non-deterministic crashes that can drive you nuts. See the answer I wrote over here for details.

worked, will try to build on this. CreateOperationWithcontext does a database update. Will try to cut short the function and test. Thank you — user2122350, Aug 13 '13 at 13:33

observeValueForKeyPath is not getting called

1 Answers1