Warning for iOS/iPhone users about duplicate NSNotification observations

Question

This isn't a question so much as a warning to others to save them some time.

NSNotificationCenter on iOS 3/iPhone OS 3 (I'm assuming also Mac OS X and iOS 4) has the following behavior:

If you register yourself multiple times for the exact specific notification, NSNotificationCenter will NOT recognize the redundancy and instead will fire off as many notifications to you as you've registered an observation for.

This is almost never the behavior you want to see and is almost always accidental.

Example:

I want my view controller to receive notifications from a singleton network object when new data comes in:

- (void) viewDidLoad 
{
    [super viewDidLoad];

    [[NSNotificationCenter defaultCenter] addObserver:self
            selector:@selector(newDataArrived:) 
                name:NewDataArrivedNotification
              object:[NetworkListener sharedNetworkListener]];
}

but earlier I'd already put the same thing in viewWillAppear:

- (void) viewWillAppear
{
    [super viewWillAppear];

    [[NSNotificationCenter defaultCenter] addObserver:self
            selector:@selector(newDataArrived:)
                name:NewDataArrivedNotification
              object:[NetworkListener sharedNetworkListener]];
}

Note that it's exactly the same notification, resolving to the same observer, sender and notification name.

In this case, if I don't remove one of those addObserver calls, I'll get duplicate notifications to my view controller.

In a multi-threaded environment, this is a world of hurt. Trust me.

Just putting this out there in case there are others who run into something like this.

Good to have the warning - you should probably put most of this in an answer and accept it :) (cue Alex Trebek mumbling something about 'must phrase your answer…') — Scott Corscadden, Mar 25 '12 at 17:43

score 3 · Accepted Answer · answered Apr 21 '13 at 02:18

NSNotificationCenter on iOS 3/iPhone OS 3 (I'm assuming also Mac OS X and iOS 4) has the following behavior:

If you register yourself multiple times for the exact specific notification, NSNotificationCenter will NOT recognize the redundancy and instead will fire off as many notifications to you as you've registered an observation for.

This is almost never the behavior you want to see and is almost always accidental.

Example:

I want my view controller to receive notifications from a singleton network object when new data comes in:

- (void) viewDidLoad 
{
    [super viewDidLoad];

    [[NSNotificationCenter defaultCenter] addObserver:self
            selector:@selector(newDataArrived:) 
                name:NewDataArrivedNotification
              object:[NetworkListener sharedNetworkListener]];
}

but earlier I'd already put the same thing in viewWillAppear:

- (void) viewWillAppear
{
    [super viewWillAppear];

    [[NSNotificationCenter defaultCenter] addObserver:self
            selector:@selector(newDataArrived:)
                name:NewDataArrivedNotification
              object:[NetworkListener sharedNetworkListener]];
}

Note that it's exactly the same notification, resolving to the same observer, sender and notification name.

In this case, if I don't remove one of those addObserver calls, I'll get duplicate notifications to my view controller.

In a multi-threaded environment, this is a world of hurt. Trust me.

Just putting this out there in case there are others who run into something like this.

This is a coder error, not a library error. Only register for the notifications you want to receive. I am not sure why you would register in the same object multiple times for the same notification. — chadbag, Dec 08 '14 at 00:17
in situations where you have a base view controller which has an observer and some other view controllers extend that base class, then if the code for adding the observer is in the view lifecycle methods like viewDidLoad or viewDidAppear, a way to avoid the observers being added to the Dispatch Table is by removing the observer and then adding it in view did load. This way the observer will not be added multiple times. — Dhiraj Das, May 15 '17 at 07:11

score 2 · Answer 2 · answered Jan 24 '13 at 07:31

2

You should and always clean up your observers.
The easiest way to do it is : [[NSNotificationCenter defaultCenter] removeObserver:self]
viewDidLoad is not a good place to add observers, because this functions may get called multiple times, this happens when viewDidUnload is triggered. A good place to put your addObservers in viewWillAppear, and removeObservers in viewWillDisappear.

answered Jan 24 '13 at 07:31

jakerz

51
4

also, viewDidUnload is deprecated and no longer even called in iOS 6 – God of Biscuits Apr 21 '13 at 02:20

score 0 · Answer 3 · answered Dec 29 '12 at 10:43

0

As you said yourself, NSNotificationCenter makes no check for duplicates, which may be annoying for some, but makes sense when concidering the full system behind it.

The same logic applies to adding targets to certain objects, but there is often a key recognition on those.

Thank you for the insight, and for a good, SEO-friendly warning :)

answered Dec 29 '12 at 10:43

Nils Munch

8,805
11
51
103

Consider the full system behind it, it makes sense? Could you please tell more detail? Thanks. – Jason Lee May 14 '13 at 03:06

Warning for iOS/iPhone users about duplicate NSNotification observations

3 Answers3

Linked