Do you need to remove notification observer in deinit

In Swift, you generally do not need to remove notification observers in deinit if you are using Swift's concurrency features. Swift concurrency provides guarantees about how callbacks are handled, which can help avoid issues related to notification observers.

For example, in the session Migrate your app to Swift 6, it is discussed how Swift concurrency can make guarantees explicit, reducing the burden on developers to manage these details manually. This includes handling callbacks and ensuring they are executed on the correct thread or actor, which can help avoid common pitfalls such as data races or memory leaks.

However, if you are not using Swift concurrency and are managing notification observers manually, it is still a good practice to remove observers in deinit to prevent potential memory leaks or unexpected behavior.

For more details on handling concurrency and callbacks in Swift, you can refer to the chapter on "Delegate callbacks and concurrency" in the session Migrate your app to Swift 6.