-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Desktop Notifications not working with Rocket.Chat+ 2.8 #7795
Comments
+1 Desktop notifications does not work at all . On the previous version (0.57.3) desktop notifications worked fine. |
+1 Changing "max room members before disabling all message notifications" from 100 to 500 fixed the issue. Max of 19 users in one of the channels. |
Using version 0.69.0 This is still an issue. Notifications just won't work no matter what client I use. |
Tested on 69 too. Better for subsquent messages, I get a flashing Rocket.Chat client. For initial message the counter remains at 0 and no-flashing even when a chat is assigned. Workaround is the new webhook on new message (not yet tested). |
Confirmed an issue. Notifications were working, then upgraded the Windows client to version 2.13.3, and notifications no longer work. Happened to everyone on the server who upgraded their client. Fixed it by going to the Help dropdown menu in the client and selecting "Reset App Data". So, maybe it's a version migration issue? |
I am having the same problem. Many people in our chat groups complaining about not receiving notifications. |
we have updated notifications logic and this should be fixed now. please let me know if this is still an issue and I reopen it. |
I've configured desktop notifications on Windows 10, Rocket.Chat+ 2.8.0, 1 instance, deployment: snap, db replicaset: ?, node: ?.
The test desktop notifications button works and shows in the bottom right corner a popup.
However, no other notifications appear. Rooms etc all default from account.
Reproduction:
Expectation:
On step 3 a popup appears.
The text was updated successfully, but these errors were encountered: