-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Does not play MP3 notification #184
Comments
You must have a command line audio player supported by the library that's being used to play the sound. Others have reported success with mplayer and mpg123. You can place it in the same folder as the program. Duplicate of #116 The pushover application token is also invalid; make sure your |
Which error? The one related to the sound player, or the one related to pushover? |
Im getting the push-over error .. |
Oh I fixed it now.. just put empty for the PUSHOVER_TOKEN |
Oh I see its an app that sends notifications.. I signed up for it and linked it thanks.. but I dont need the token just the key Also it seems like it is not searching Nvidia and I put that under the "stores" in the .ENV file |
Upon running npm run test:notification
I get a code break..
and my .env file has this PLAY_SOUND="promise.mp3"
with the mp3 file in the nvidia-snatcher folder
[5:01:23 PM] error :: error playing sound: Error: Couldn't find a suitable audio player
C:\nvidia-snatcher\node_modules\pushover-notifications\lib\pushover.js:146
throw new Error(d.errors[0], res)
^
Error: application token is invalid
at Pushover.errors (C:\nvidia-snatcher\node_modules\pushover-notifications\lib\pushover.js:146:13)
at IncomingMessage. (C:\nvidia-snatcher\node_modules\pushover-notifications\lib\pushover.js:250:12)
at IncomingMessage.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1252:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test:notification:
npm run build && node build/__test__/notification-test.js
Possible solution
The text was updated successfully, but these errors were encountered: