Matthieu Lemoine

`push-receiver` needs to access `android.clients.google.com` and `mtalk.google.com`. According to the site you've shared, they work in China. Do you see any error ?

Could be nice. If someone wants to implement this feature, it should be made in [push-receiver](https://github.com/MatthieuLemoine/push-receiver).

@arun-nfactorial well you have two ways of doing that : - Easy: Pass a fake webContents in setupPushReceiver : you just need a object with a send function which will...

@arun-nfactorial Never tried on Windows. Did you receive the notification and it's just a display issue or the notification is never received ?

A) Yes. Something like : ```javascript const webContents = { send : (event, data) => doSomething(event, data) } ``` B) You can start from the main process using `ipcMain.send(START_NOTIFICATION_SERVICE, senderId);`....

@arun-nfactorial A 200 doesn't mean that the notification was delivered. It's an async operation. A 200 only means that the device token & the server key is valid.

So it's an issue with electron's Notification API ?

There are requirements depending on the Windows version https://electronjs.org/docs/tutorial/notifications#windows

@mjarkk Feel free to send a PR to fix this

[push-receiver](https://github.com/MatthieuLemoine/push-receiver) does generate an id for each registration [here](https://github.com/MatthieuLemoine/push-receiver/blob/master/src/register/index.js). In [electron-push-receiver](https://github.com/MatthieuLemoine/electron-push-receiver), a new registration is created only if we didn't register before or if the credentials have been cleared. See...