RocketChat / RocketChat/Rocket.Chat

notifications not sending in browser

Open
#13,720 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

No notification pops up in browser when new messages. When first enterring Rocket Chat, it ask for permision to send me notifications. I never see / receive none.
The messages are sent / received correctly by all users in the room, but you have to visit the room in order to see if there are new messages.
The javascript Iframe listener detects the activity ( althought it detects it 3 times, instead of only once, strange behavior. We have a point system and want to award users for being active in chat, receiving a triplicated message in javascript its a problem for us )
Notifications fail in Iframe and directly in server url.

Steps to reproduce:
  1. Enter any room
  2. Send any type of message
  3. The rest of the room participants should be notificated about new message, but no notification is sent to users.
Expected behavior:

Send / Receive notifications about new messages and activity in lobby as advertised in https://rocket.chat
Easy way to keep track of activity in several Rooms.
sidebars@2x **Image from https://rocket.chat

Actual behavior:

Nothing changes regardles of new messages, users in room, ... ( and besides sometimes rooms are duplicated -> issue: 13715 )
no_notification

Server Setup Information:
Version of Rocket.Chat Server: 0.74.2
Operating System: Linux x64, Ubuntu 18.04
Deployment Method: snap
Number of Running Instances: 1
DB Replicaset Oplog: Info not available in Rocket Chat Info (or badly translated to Spanish), so maybe it could be added in the future.
NodeJS Version: v8.11.4
MongoDB Version: Info not available in Rocket Chat Info (or badly translated to Spanish), so maybe it could be added in the future.
Additional context

Seems that the sidebar is buged.

Relevant logs:

No relevant error log.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in a browser using the listed steps, both in an iframe and at the direct server URL, with Rocket.Chat 0.74.2. Inspect the browser notification and sidebar behavior, including the reported triplicated iframe activity and the related issue 13715. Done means new-message notifications appear reliably without duplicate activity events or duplicated rooms.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.