Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

toaster does not work on Windows 10 version 1709 #206

Closed
devkoriel opened this issue Oct 18, 2017 · 9 comments
Closed

toaster does not work on Windows 10 version 1709 #206

devkoriel opened this issue Oct 18, 2017 · 9 comments

Comments

@devkoriel
Copy link

I tested the node-notifier on following environment using npm run example:windows command.

  • Windows 10
  • Version 1709
  • OS Build 16299.19

However, a toast never shows up. When I test it on older version of Windows, it works perfectly.
Any others have the same issue?

@vadim1884321
Copy link

The same, I rolled back to the previous version of 1703

@devkoriel
Copy link
Author

Running SnoreToast.exe directly from command line works very fine on 1709 but toaster.js doesn't.

@Revadike
Copy link

I can confirm. I just updated Windows and no more notifications :(

@verget
Copy link

verget commented Nov 1, 2017

I had a similar problem, solved with anthonyraymond comment

@Revadike
Copy link

Revadike commented Nov 2, 2017

Could you please be more specific in what I need to do to fix it?

@sarathy-partha
Copy link

sarathy-partha commented Nov 11, 2017

I am using,

  • Windows 10
  • Version 1709
  • OS Build 17025.1000

Works for me if I use 'Custompath' to 'toast' instead of 'SnoreToast'. Here is the code

var notifier = new WindowsToaster({
    withFallback: false, // Fallback to Growl or Balloons?
    customPath: 'C:\\Users\\<UserName>\\Downloads\\toaster\\toast\\bin\\Release\\toast.exe' // Relative/Absolute path if you want to use your fork of SnoreToast.exe
});
notifier.notify({
        title: "Title",
        message: "Message",
        wait: false, // Wait for User Action against Notification or times out. Same as timeout = 5 seconds
        appName: "app.id"

    }, function (error, response) {
        console.log(error, response);
    });

@mdcfe
Copy link

mdcfe commented Nov 15, 2017

By running SnoreToast manually then setting appName: Snore.DesktopToasts, I was able to get SnoreToast notifications working again without using a customPath.

@TimmoUK
Copy link

TimmoUK commented Nov 19, 2017

Hi, I am using SnoreToast in a simple compiled batch file. After 1709, my exe never returned to my code after the SnoreToast request. The problem was resolved by stopping passing over appid. My previous code was:

snoretoast -t "NAS %nasname%" -m "Shared storage mapped to drive %drive%" -appid MapNAS -p ls-wxl.png -w

Now I am using:

snoretoast -t "NAS %nasname%" -m "Shared storage mapped to drive %drive%" -p ls-wxl.png -w

The appid in the toast message appears as SnoreToast (previously MapNAS).

@mikaelbr
Copy link
Owner

This should work as expected now. Reopen if any issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants