electron/atom
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
..
app chore: rename atomBinding to electronBinding (#17419) 2019-03-18 12:37:06 -07:00
browser fix: use a more unique identifier for NSUserNotification instances (#17469) 2019-03-20 09:53:20 -07:00
common fix: check the result when calling js function (#17443) 2019-03-20 08:27:06 -07:00
renderer fix: check the result when calling js function (#17443) 2019-03-20 08:27:06 -07:00
utility More migration of ServiceContext to ServiceBinding 2019-02-14 23:59:22 +05:30