Home > Articles > Programming > General Programming/Other Languages

Quis custodiet ipsos custodes? Going Heisenberg on iOS' NSNotificationCenters

You may think your observers are well behaved, but are they? With modern block-based NSNotificationCenters, you may be leaking without ever realizing it. Erica Sadun shows how to clean things up.
Like this article? We recommend

Mea culpa. I have been abusing and misusing iOS’s block-based notification handlers repeatedly. For years I’ve been working under the mistaken impression they operated like the classic target-action version. That is, I assumed I could clean up after myself in dealloc by removing myself as an observer. I was wrong. The following dealloc approach won’t work for these handlers.

- (void) dealloc
    [[NSNotificationCenter defaultCenter] removeObserver:self];

If you’re playing along here, please feel free to make rude buzzing noises or squirt me with virtual seltzer water. This approach is perfectly fine for classic notifications, namely the ones you create with target-action. In the old-style system, you supplied a selector and a notification name and you implemented the handler in a separate method.

[[NSNotificationCenter defaultCenter] addObserver:self 
    name:kNotificationName object:nil];

With blocks, however, you are not the observer. The observer is built on your behalf as a new object. If you’re calling the following method without catching the new observer, you’re leaving a trail of orphaned handlers behind you.

id observer = [[NSNotificationCenter defaultCenter] 
    addObserverForName:kNotificationName object:nil 
    queue:[NSOperationQueue mainQueue] 
    usingBlock:^(NSNotification *note) {
        // implementation here

Cleaning Up Observers

As with old-style handlers, it’s up to you to remove observers from the notification center when your object deallocates. I’ve started using a mutable observers array, adding each newly established observer to it whenever I create a notification handler. This array enables me to iteratively unload observers in my dealloc method, as simply as I used to remove myself as an observer:

- (void) dealloc
    for (id observer in observers)
        [[NSNotificationCenter defaultCenter] removeObserver:observer];

The observers array offers a simple and reliable approach for handlers that persist throughout a view controller’s lifetime. I establish observers, typically in viewDidLoad or loadView, and they function until the controller is dismissed. You’ll read about short-lived observers later in this write-up.

Working with Blocks

Using a block-based approach for notification handlers provides fundamental advantages. It encapsulates the notification handler implementation at the physical location where the notification observer is defined. That union simplifies both code design and review. Should you need to update or even remove functionality, all elements of the notification and its handler are centralized to a single position in your code.

Being block-based however, comes with costs. For one thing, you must take care not to create self-referential retain cycles. Any reference to self, whether directly stated or through property use (as in Figure 1) can prove problematic. This kind of development overhead isn’t an issue when using the older target-action approach.  Prepare to change your best practices when applying blocks.

Figure 1 Beware of block-based retain cycles

Although Xcode is getting better and better at spotting block issues (as in Figure 1), block hygiene still rests on your shoulders. Here are the key rules for working with notification handler blocks.

  • To avoid retain cycles, establish a weak self reference outside any block that uses self in its code.
__weak typeof(self) weakSelf = self
  • Create a strong reference to that weak version as the first line in your block. If self still exists when the block starts to execute and hasn’t fallen back to nil, this next line ensures it persists throughout the block’s execution lifetime.
__strong typeof(self) strongSelf = weakSelf;
  • Translate all direct and indirect self references to strongSelf. Instead of calling [self method], use [strongSelf method]. For properties avoid using calls like the _originalTransform you saw in Figure 1. Replace these with strongSelf.origialTransform dot notation.

Short-Term Observers

Many notification observers persist for long periods of time. Most are intended to provide background handlers for external events, so it makes sense to keep them active for as long as your object is around to handle them.

In other cases, you’ll want to remove the observer as soon as some event triggers. For example, you might enable some user-directed event and then respond to it by listening for a notification. Using notifications enables you to avoid using cross-class dependencies. For example, you might fire a notification when a gesture finishes recognition or when a dynamic animation completes.

After the handler block executes, clear the observer and its associated block from memory by cleaning up the trigger-then-dispose mechanism. This approach ensures stale handlers won’t repeatedly fire and prevents lingering handlers from producing extraneous results when you least expect them.

With this approach, as with long-term listeners, expect block-based complications. In this case, the challenge lies in ensuring you properly remove your observer. As you’ll see, transferring the observer reference to block code requires finesse. The following snippet listens for the end of a dynamic animator sequence. When complete, it re-enables the right bar button and removes a temporary observer from the notification center.

// Declare the temporary observer as a __block variable
id __block temporaryObserver = nil;

// Establish the weak self reference
__weak typeof(self) weakSelf = self;

// Create the notification handler
temporaryObserver = [[NSNotificationCenter defaultCenter] 
    object:nil queue:[NSOperationQueue mainQueue] 
    usingBlock:^(NSNotification *note) {

    // Establish the strong self reference
    __strong typeof(self) strongSelf = weakSelf;

    // Perform the work (re-establish the bar button)
    strongSelf.navigationItem.rightBarButtonItem.enabled = YES;

    // Remove the observer
    [[NSNotificationCenter defaultCenter] removeObserver:temporaryObserver];

Any variable marked by the __block storage attribute is shared between the calling method and the block that uses it. Here it’s vital to create your observer with that __block variable storage. This approach enables the block to use the value assigned to the temporaryObserver variable after the block has been established.

When running the previous snippet, the block is created first in the steps to establish the notification handler. Unless otherwise specified, it uses the initial value of the temporaryObserver variable. This is set to nil. Next, the block is added to the notification center. Only then is the new observer returned, to be stored into temporaryObserver.

Without the __block attribute, the value is used as-is, that is, as nil. By enabling the block to access the variable storage, you permit its code to see the value assigned after the add-observer method returns and whenever the handler executes.

You can best see this in action by logging your observer in the block. When using the __block storage type, the observer is properly established:

2014-03-24 10:44:54.382 Hello World[8800:60b] Removing observer <__NSObserver: 0x9b63ae0>

But without that attribute, you’ll inadvertently leak. The temporaryObserver remains nil and is never removed from the notification center.

2014-03-24 10:50:35.439 Hello World[8873:60b] Removing observer (null)

Wrapping Up

Never be afraid to use block-style notification handlers. Although you’ll encounter extra overhead, it’s not hard to apply best practices. The lessons here are simple. Here’s a quick summary of tips from this write-up:

  • When using block-based notification handlers, avoid self-referential retain cycles. Apply these to both explicit and implicit self references.
  • Keep track of all observer objects created by the notification center.
  • Release long-term observers in dealloc. Release short-term observers in the handler block via __block variable references.

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.


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.


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.


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.


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


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


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.


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.


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