electron/atom/browser/notifications
Samuel Attard 45d90e77b7
fix: use a more unique identifier for NSUserNotification instances (#17469)
So although apple has it documented that notifications with duplicate identifiers in the same session won't be presented.  They apparently forgot to mention that macOS also non-deterministically and without any errors, logs or warnings will also not present some notifications in future sessions if they have a previously used identifier.

As such, we're going to truly randomize these identifiers so they are
unique between apps and sessions.  The identifier now consists of a
randomly generated UUID and the app bundle id.
2019-03-20 09:53:20 -07:00
..
linux build: auto-gen libnotify_loader.cc (#15648) 2018-11-10 14:21:40 -05:00
mac fix: use a more unique identifier for NSUserNotification instances (#17469) 2019-03-20 09:53:20 -07:00
win feat: Upgrade to Chromium 71.0.3578.98 (#15966) 2019-01-11 17:00:43 -08:00
notification.cc
notification.h
notification_delegate.h
notification_presenter.cc
notification_presenter.h
platform_notification_service.cc Use base::BindOnce in notifications code 2019-03-08 15:04:32 -08:00
platform_notification_service.h Use base::BindOnce in notifications code 2019-03-08 15:04:32 -08:00