-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
SnoreToast is added to the start menu when notifying on Windows #2720
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
Comments
I had no idea what it was when I found it in my start menu, so when I ran it and it ran some scripts in a console window that appeared just for a fraction of a second, I suddenly wasn't sure it's not malware... IMO it shouldn't add a new shortcut, or if it does, and the user starts it directly, it should display a notification that reads something like "This app is used by other apps to display notifications" |
Yeah, def not cool. Ran across this just now. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
https://msdn.microsoft.com/en-us/library/windows/desktop/hh802762 |
What a mess. But why did this just suddenly show up to me today??? It's June 2019... |
Another vote to remove this. A command-line program should notify the user via the command-line. |
Agree with jcsston |
I agree, this is outrageous and the shortcut should not be created! @Riccarr |
I am semi-okay with the shortcut. After this issue specifically Or call it something other than SnoreToast. Like NodeNotifier, so I know where the heck it came from. @Riccarr, while I completely disagree with your tone, you do have a point.
But to that point, why would you run some random software that is maintained by a community you're not a part of, that can install random shit on your start menu? AKA: Why would you run any open-source software, including vue, ever? Because we're programmers! That's why! The breadth of our curiosity has no bounds. Also, I thought I had maybe installed the program along with three others yesterday and hadn't uninstalled it. So I was trying to see what it was. I couldn't remember what I had or had not installed. When the application closed, I was suddenly afraid that it was running large scripts in the background. And if running the executable by itself popped up a notification about what SnoreToast was, then I would have known what the program was and probably wouldn't have been bothered by it at all. |
Is this ever going to be addressed. Only noticed it because the project creation got stuck on it. Kind of weird to add something like this without telling the user explicitly. |
If anyone ever decides to get around to implementing this, I'd like to add a feature request for the install process to ask where the user would like that shortcut to be created, because it is rather tedious to clean up and reorganize a start menu after every self-important application decides it belongs in the root of the start menu, and then recreates the same shortcut on every single update. I'd much rather have it down in my dev tools sub-menu... |
+1 fix this please. I still get this on my start menu in Win10. And the branded SnoreToast notifications that just start coming up on Windows 10 look pretty much like your box has been pwned. |
+1 to this! Two years and not fixed yet.... |
I thought today I had a virus or something because of this man |
not really happy with random stuff getting installed without informing/consent!!! I am installing vue and cli. It shouldn't have anything to do with random notifications popping up. If anything why not just output the error in command line like others? |
Got quite spooked today too when i opened it and a terminal popped up. |
It's labeled as "contribution welcome". |
+1, I too found this in my start menu and immediately thought it was malware. |
Same! |
just saw this pop up found exe, deleted, deleted shortcut. don't install garbage without my explicit permission to do so. |
Seriously, not sure it's legal in Europe! |
How is this still not fixed...? |
Its easier to uninstall McAffee than this thing... jesus christ. |
this is not cool, please fix this thing |
I got shocked that I might have malware on my pc. It is very unprofessional to add such a shortcut to start without notifying the user and very bad for Vue's reputation. |
Why does nobody open a PR to remove it? |
Yeah, rly not cool of them ;/ And I thought that it is a malware. |
Just installed itself in my Windows menu. NOT cool at all. |
@Legion2 Read the comments, that's why. Windows 8+ requires the start menu to be populated to have notifications appear. I think the best solution right now would be to make a postuninstall script to remove this start menu entry. Although ideally that code will have to reside in SnoreToast repo. Alternatively, node-notifier could change it's API to allow passing additional config to specify an app ID so it installs using a different app name based on the package using it. And the uninstall code can reside in this repo itself calling that specific app name to be removed from startup entry. |
This prevents SnoreToast from installing a Start Menu shortcut by specifying an appID. The appID is also used to set the notification's title bar text in Windows 10. That text is now set to "Vue UI", which replaces the default value of "SnoreToast". fixes vuejs#2720
The solution is to provide an Once this fix lands, users may want to manually undo the SnoreToast changes from their system, as described below. Remove SnoreToast shortcut from Start MenuOption A: File Explorer
Option B: Windows Command Line
Remove SnoreToast's registry keyNote: SnoreToast sets a registry key in order to register its notification center. The UUID seen in the key is for SnoreToast v0.7.0. Option A: Registry Editor
Option B: Windows Command Line
|
It's been more than 2 years now but still no official solution to this problem. I just closed 3 tabs before coming to this issue. |
Wel the PR fixcing it is only 17 days old so there is a solution just not ofcal yet |
This prevents SnoreToast from installing a Start Menu shortcut by specifying an appID. The appID is also used to set the notification's title bar text in Windows 10. That text is now set to "Vue UI", which replaces the default value of "SnoreToast". fixes #2720
This prevents SnoreToast from installing a Start Menu shortcut by specifying an appID. The appID is also used to set the notification's title bar text in Windows 10. That text is now set to "Vue UI", which replaces the default value of "SnoreToast". fixes #2720
Damn I thought it was malware or something like that :((( |
I thought I downloaded some bloatware or something from installing apps |
Same here, thought it was malware or a virus when I found it, I was immediately suspicious of it. |
same |
same |
WTF? Why you install applications on my computer without prompting? |
Version
3.0.4
Node and OS info
Node v9.4.0, npm v5.6.0, Windows 10
Steps to reproduce
@vue/cli
on Windowsvue ui
on a project%APPDATA%\Microsoft\Windows\Start Menu\Programs
now has a SnoreToast shortcutWhat is expected?
SnoreToast would not have a shortcut since the user may not like its addition to their start menu without indication of its purpose.
Additionally, the notification should trigger the first time, but I'm guessing this is caused by SnoreToast failing to notify without an app ID in the start menu to use for the notification.
What is actually happening?
The shortcut is installed without an opt-in, notification fails the first time
The UI's notification API uses
node-notifier
which in turn usesSnoreToast
for native Windows notifications.SnoreToast seems to indicate that a program in the start menu is necessary for notifications, though I can't find anything to back up that it needs to be in the start menu in case SnoreToast can be used from the
node_modules
folder.If the CLI was an Electron app, the intended use of
node-notifier
would be to use the shortcut for the CLI instead (which would fix also fix the issue with it not firing and it saying the wrong app name when notifying). Since there isn't a shortcut for the CLI, it sounds like a workaround would need to be found to keep the implementation the same.The issue with it not firing the first time is most likely related to and could be fixed by "installing" the shortcut before the first notification.
The text was updated successfully, but these errors were encountered: