The default behavior of iOS is to not show a notification (like the kind that comes in through your phone’s lock screen or Notification Center) if the app is in the foreground. I’m working on a ticket for the Lyft app to show or suppress notifications that come in while the app is in the foreground. iOS 10 introduced a whole new
UserNotification framework that lets us do just that!
The delegate of our notification center will get a call aptly named
userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void). Since we always have to call the completion handler – and that parameter defines the type of presentation we want – we can now control the notification’s display.
In Objective-C the options are so:
But in Swift,
UNNotificationPresentationOptionsNone is not available. In fact, you can only really see the docs for this option at this page. It’s listed as a Global Variable, and not a member of an enumeration. There’s a separate page for the
So I fired up a sample project and made a method that returned None from Objective-C and bridged that over to Swift. Of course it works, and the raw value is 0. So the options for my ticket are either add Objective-C back into the project (all our code is Swift) just to bring this over, or make a local variable set to a raw value of 0. The latter is likely what I’ll end up doing.
I’ve filed radar 36166279 to address this.
After posting this, Jake Carter replied to me on Twitter with an idea:
Have you tried setting a no options value via ? See the ‘noOptions’ example in the Using an Option Set Type section of https://t.co/UPct7ImcyM— Jake Carter (@JakeCarter) December 21, 2017
When I got in to the office this morning I gave it a go and it worked! I’ve used the
 syntax before so I’m a little disappointed that I didn’t remember it. I plugged that into my sample app and its
rawValue turned out to be 0. So now I don’t have to choose between two bad options.
I think what tripped me up was seeing that the Objective-C version was an enumeration coupled with me not seeing that the Swift structure conforms to
OptionSet. If I had slowed down for just a couple of minutes then I might have noticed.
I think I’m going to leave the radar open, though. I will probably amend it with these findings and make it more of a documentation issue rather than needing to add a new option to the
UNNotificationPresentationOptions type. Thanks Jake!