-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Read receipts not working #15484
Copy link
Copy link
Closed
Labels
area: ui/uxRelated to UI/UX, frontend code, accessibility, and user interactionRelated to UI/UX, frontend code, accessibility, and user interactiontype: bug
Description
Description:
After updating to 2.1.0 the read receipts are not displayed anymore. No checkmark in browser, and only grey checkmarks in the app. No blue checkmarks after a message is read.
Also when showing message info, only the person who send the message is shown in the list.
Steps to reproduce:
- Direct chat or group chat
- open message context menu, select info
- only the person who wrote the message is shown, no one else, even if the message has been read
Expected behavior:
- message read receipt shown in info
- blue checkmark in direct chat
Actual behavior:
- In group chats: only the person who wrote the message is shown, no one else, even if the message has been read
- in direct chats no blue checkmark appears
Server Setup Information:
- Version of Rocket.Chat Server: 2.1.0
- Operating System: 4.19.72-gentoo, Ubuntu 18.04 LTE (tested on two systems)
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: v8.15.1
- MongoDB Version: 4.2.0
Additional context
- could be related to changes in [IMPROVE] Add missing indices used by read receipts #15316
- could be a problem on our end because using MongoDB 4.2.0
Relevant logs:
Server log when accessing "info":
Meteor ➔ method getReadReceipts -> userId: RQySce2mbjTpGyxGt , arguments: [ { messageId: '4cce12f2-60f4-443f-b253-46043a799eae' } ]
Meteor ➔ method canAccessRoom -> userId: RQySce2mbjTpGyxGt , arguments: [ 'THG8ez3NKvCi9WoYv', 'RQySce2mbjTpGyxGt' ]
Reactions are currently unavailable
Metadata
Metadata
Labels
area: ui/uxRelated to UI/UX, frontend code, accessibility, and user interactionRelated to UI/UX, frontend code, accessibility, and user interactiontype: bug