Where to remove observer for NSNotification in Swift?

Clement Joseph picture Clement Joseph · Feb 24, 2015 · Viewed 71.3k times · Source

Where should I remove the observer for NSNotification in Swift, since viewDidUnload and dealloc() are unavailable?

Answer

Nikola Milicevic picture Nikola Milicevic · Oct 31, 2016

As of iOS 9 (and OS X 10.11), you don't need to remove observers yourself, if you're not using block based observers though. The system will do it for you, since it uses zeroing-weak references for observers, where it can.

And if you are using block based observers, make sure you capture self weakly using [weak self] in the closure's capture list, and remove observer in deinit method. If you don't use weak reference to self, deinit method (and thus removal of that observer) will never be called since Notification Center will hold a strong reference to it indefinitely.

More info can be found at Foundation Release Notes for OS X v10.11 and iOS 9.

If the observer is able to be stored as a zeroing-weak reference the underlying storage will store the observer as a zeroing weak reference, alternatively if the object cannot be stored weakly (i.e. it has a custom retain/release mechanism that would prevent the runtime from being able to store the object weakly) it will store the object as a non-weak zeroing reference. This means that observers are not required to un-register in their deallocation method.

Block based observers via the -[NSNotificationCenter addObserverForName: object: queue: usingBlock] method still need to be un-registered when no longer in use since the system still holds a strong reference to these observers.