RocketChat / RocketChat/Rocket.Chat
Unread messages.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Desktop client. Message was read in client, windows is active. But notify arrived on mobile.
Steps to reproduce:
Expected behavior:
Actual behavior:
Server Setup Information:
Version of Rocket.Chat Server: 3.8.0
Operating System: Ubuntu 18.04
Deployment Method: Docker
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version: 12.18.4
MongoDB Version:4.0.21
Client Setup Information
Desktop App or Browser Version: MacOS
Mobile: iOS
Additional context
ScreenShot
Relevant logs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no files, tests, or entry points, and its reproduction, expected behavior, and actual behavior sections are empty. Start by reproducing the notification behavior with the listed Rocket.Chat 3.8.0 server and desktop, iOS, and Docker setup; done means a read message in the active desktop client does not trigger an unexpected mobile notification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ios, macos, mongodb, node.js, typescript
- Domain
- backend, desktop, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100