Implementing removable remote notifications on iOS

Photo by Youssef Sarhan on Unsplash

Most of the apps we create have some form of notifications. They can be either local or remote – sent from backend via APNS. There are some cases where we would want to remove notification from user’s phone after some condition is met, e.g.

  • It’s not valid anymore, e.g. we sent a notification with an offer which ended before user read it.
  • We have a chat application and user already read the message on another device or our website.

Fortunately, it’s suprisingly easy to do with UserNotifications framework introduced with iOS10.

To try this yourself, you need active Apple Developer account, as working with push notifications requires that.

Firstly, create new iOS app Xcode project. It doesn’t matter what kind, we won’t leave AppDelegate.swift file :). After creating the project, turn on Push Notifications in Capabilities section of your target settings. You’ll also need to turn on Background Modes capability and check Remote notifications mode. One last step is to create Sandbox APNS certificate in Apple Developer Portal.

Now, let’s jump into the code. Replace your AppDelegate with this snippet:

Let’s go through it. In application:didFinishLaunchingWithOptions: we just register for notifications and prompt for authorization from user. application:didRegisterForRemoteNotificationsWithDeviceToken: converts device token to hex form and prints it. This will allow us to send pushes from our command line. For now, let’s skip application:didReceiveRemoteNotification:fetchCompletionHandler: as it doesn’t make much sense without some introduction.

UNUserNotificationCenter has a method which allows us to remove delivered notifications with specified ids. It’s easy when dealing with local notifications, as we are responsible for providing identifiers for them. On the other hand, remote notifications have random identifiers generated by APNS. There is only one exception from that — if we specify apns-collapse-id header in our request to APNS, it will send notification with identifier equal to value of this header. Normally, apns-collapse-id is used to create notifications which should be replaced with newer ones, but this nice behavior (which is documented, so don’t worry ;) — will allow us to send notification with specific id. To do that, just run some cURL command in your Terminal:

This will send notification with identifier set to 1234. Great, we are halfway done! Now we just need to trigger our app to remove specified notification on demand. And now we can go back to application:didReceiveRemoteNotification:fetchCompletionHandler: method. This method is always called when app receives push notification with special field in its payload: content-available with value 1 (why not true? Ask Apple). Our implementation searches notification’s payload for del-id field which contains id of notification to delete. With that id available, we can remove notification with UNUserNotificationCenter.current().removeDeliveredNotifications(withIdentifiers: [idToDelete]). Now, our app is ready to remove notifications from users’ phones! Just send triggering push with del-id set to our previous notification’s id — 1234. This notification doesn’t have any alert or sound so it won’t be visible to user.

We are done! Let’s enjoy our creation:

I hope this short tutorial will be useful to you, but don’t overuse this, you users might get confused when their notifications start to dissapear. Cheers!