electron: Windows does not display Notifications

Electron version: 0.37.3
Operating system: Windows 10 Build 10586.104

I’ve been trying to figure out if I’m missing something or anything, but since the docs only state that they “just work” on windows 10 I’m at a loss here. Notifications show fine for osx and linux, just not on windows 10. I can even go into the devtools and type new Notification("testing", { body: "testing" }); and nothing happens. Do I need to make an installer or do I have to set the application user model id? Or might the packager screw it up?

EDIT: I can rule out the packager, just did an npm install with electron-prebuilt 0.37.3 -> ran electron main.js -> created a new notification in devtools and no avail.

I can reproduce this with the electron-quick-start example app using the version set in package.json (^0.36.0) or setting it to 0.37.3.

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 3
Comments: 27 (19 by maintainers)

Commits related to this issue

Update brightray for #4973 — committed to electron/electron by zcbenz 8 years ago

Most upvoted comments

while using application name as notifier’s ID, everything works.

Hmm I’m wrong here, when using application name as notifier’s ID, it is actually telling Windows our AppUserModelID is the application name, which works because it has been used as AppUserModelID by old versions of Electron before.

The magic thing is, if we ignore get_Setting and send a notification anyway, the notification will show and following notifications with the same AppUserModelID will also work. But if we check get_Setting in the first time, it will always return DISABLED.

zcbenz on Apr 15, 2016

After biset the commits, I can confirm this is caused by electron/brightray@242feb1. The key of debugging is, make sure you change the AppUserModelID to a new value every time, otherwise Windows itself might be confused and give random results.

zcbenz on Apr 15, 2016

Yes, as far as I’m concerned, they’re all on. Screenshot I’ve tested it inside a VM using the latest ISO from the Microsoft website, so no settings have really been changed. I’ve also updated to latest build (10586.164) but to no avail. Maybe because I haven’t inserted activation code yet?

kumpelblase2 on Apr 1, 2016