Read receipts not working #15484

phriedrich · 2019-10-02T08:58:22Z

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' ]

The text was updated successfully, but these errors were encountered:

robopossum · 2019-10-02T15:25:04Z

I am also experiencing this on

OS : Debian 9.9
MongoDB Version : 4.0.11
NodeJS Version : v8.16.0

Yures · 2019-10-02T19:21:52Z

Same issue. RC docker 2.1.0 Mongo docker 4.0.11

…

2 окт. 2019 г., в 18:25, robopossum ***@***.***> написал(а): I am also experiencing this on OS : Debian 9.9 MongoDB Version : 4.0.11 NodeJS Version : v8.16.0 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

dca-adam · 2019-10-03T01:42:21Z

I am also experiencing this issue on both my test and prod environments.

Version of Rocket.Chat Server: 2.1.0
Operating System: CentOS 7.7.1908
Deployment Method: tar
Number of Running Instances: 1 (test and prod are independent instances)
DB Replicaset Oplog: Enabled
NodeJS Version: 8.11.4
MongoDB Version: 3.6.14

johnbrown-yoti · 2019-10-03T02:32:09Z

Same issue here.

Rocket.Chat Version: 2.1.0
NodeJS Version: 8.11.3 - x64
MongoDB Version: 3.6.14
Deployment Method: tar
Number of Running Instances: 3
ReplicaSet OpLog: Enabled

gennari-dkt · 2019-10-08T09:26:40Z

Same issue for me.

Version of Rocket.Chat Server: 2.1.0
Operating System: Debian 9.9
Deployment Method: tar
Number of Running Instances: 1 (test and prod are independent instances)
NodeJS Version: 8.11.4
MongoDB Version: 4.0.10

bkraul · 2019-10-09T20:34:18Z

Same issue here with develop (da6025e)

Version of Rocket.Chat Server: 2.2.0-develop
Operating System: Ubuntu 18.04 (docker)
Deployment Method: docker (develop tag)
Number of Running Instances: 1 (test and prod are independent instances)
NodeJS Version: v8.15.1
MongoDB Version: 4.0.12

I had posted an update where it seemed the problem was on only one DM channel, but no, it is across the board. Read receipts are not working at all, even when on in the system.

reetp · 2019-10-15T15:59:18Z

This works in Custom CSS

.color-component-color {
    color: red !important;
}

Just curious. Why is it seeming to use use the 'Old' Colors and not the 'New' ones?

geekgonecrazy · 2019-10-16T00:34:58Z

@ggazzo @tassoevan just making sure this is on your radar. Seems like css issue

wreiske · 2019-10-16T00:46:08Z

This is NOT a CSS issue. I think the index added in #15316 doesn't allow multiple messageId's.

All of my db.rocketchat_message_read_receipt's show multiple items PRE upgrade. Now there is only one read receipt per message. The reason the blue check isn't showing is that all users haven't read the message.

I am only getting the owner of the message showing on the new read receipts in the database.

bkraul · 2019-10-16T01:32:01Z

The reason the blue check isn't showing is that all users haven't read the message.

I am positive all users in the DM conversation have read all messages that should be showing "read" but are not.

wreiske · 2019-10-16T01:34:27Z

The reason the blue check isn't showing is that all users haven't read the message.

I am positive all users in the DM conversation have read all messages that should be showing "read" but are not.

Technically, they have not read the messages because RocketChat isn't saving that they read them. Only one read reciept is being saved per message. That is what I meant.

bkraul · 2019-10-16T01:36:03Z

Oh I got you. Apologies.

phriedrich · 2019-10-17T22:32:31Z

Thanks to anyone involved fixing this. I can confirm it's working again.

wreiske · 2019-10-22T20:18:55Z

Ahh I think the read receipts are still not working 100% of the time because we have rocket.cat in the channels. rocket.cat isn't reading the messages like it used to :'(, so the check never goes blue.

reetp · 2019-10-22T22:54:01Z

I am only getting the owner of the message showing on the new read receipts in the database.

On 2.1.1

Is that still true?

"Info" only shows the owner having read a group message even though they must have all read it.

Wirone · 2019-10-23T07:20:58Z

We've updated to 2.1.1 and read receipts are working properly (information modal displays list of users who read the message), but as @wreiske said, bots cause that blue tick is not shown because they don't mark messages as read. Minor issue, but would be great if this could be fixed (maybe just ignore users with bot role when determining if tick should be displayed?).

rodrigok · 2019-10-23T12:21:54Z

Good catch @Wirone we will check this.

@wreiske are you sure that your rocket.cat was reading the messages before? The only way I can see this happening today is if you use the APIs to call the readMessages for the rocket.cat user manually via some integration or so.

wreiske · 2019-10-23T12:45:35Z

As it is right now with the latest 2.1.1 update.

When I go back to older messages that were sent during the 2.1.0 read brokenness, I only see one person, the original author. The check is blue.

When I go back to older messages, BEFORE 2.1.0 read brokenness, I see everyone that had read the message. The check is blue.

In a channel where rocket.cat has been invited in, BEFORE 2.1.0 read brokenness, rocket.cat read all messages after they were sent

Here's a message on 2.1.1 that shows the blue check, however, not everyone has read the message... or at least, the UI isn't showing everyone that has read it.

There are 16 users in this channel. Why is the check blue?

rodrigok · 2019-10-23T20:04:48Z

@wreiske not sure if this will help. I could not reproduce your case of having a message marked as read with just a few participants.

GoetheG · 2019-11-22T09:31:02Z

Shouldn't this issue be merged with all the other same isses? Cause this error still occurs with the latest version.
#4957
#15656
#15484

gerroon · 2020-04-25T18:53:05Z

I do not see readd receipts with my setup. This used to work but when I do not remember.

3.0.12
Apps Engine Version	1.12.0
Database Migration	174
Database Migration Date	April 13, 2020 5:50 PM
Installed at	June 16, 2019 10:29 PM

OS Type	Linux
OS Platform	linux
OS Arch	x64
OS Release	5.4.0-4-amd64
Node Version	v12.14.0
Mongo Version	4.0.12
Mongo Storage Engine	mmapv1

kgdemir · 2020-09-15T15:27:28Z

Read Receipts is Broken again, when I try to look any message before 3.6.0 update I can see individual receipts, but after the update it is just showing receipts for sender and current logged in account

phriedrich · 2020-09-15T15:48:34Z

There's already a ticket for the new error: #18689

reetp mentioned this issue Oct 15, 2019

Read Receipts are not showing on 2.1.0 #15578

Closed

geekgonecrazy assigned tassoevan and ggazzo Oct 16, 2019

geekgonecrazy added ui/ux type: bug labels Oct 16, 2019

geekgonecrazy mentioned this issue Oct 16, 2019

[FIX] Subscription record not having the ls field #14544

Merged

geekgonecrazy mentioned this issue Oct 16, 2019

[FIX] Remove unique index from read receipt messageid #15601

Closed

rodrigok mentioned this issue Oct 17, 2019

[FIX] Read Recepts was not working #15603

Merged

rodrigok closed this as completed in #15603 Oct 17, 2019

rodrigok mentioned this issue Oct 23, 2019

[FIX] Read Receipts were not working properly with subscriptions without ls #15656

Merged

reetp mentioned this issue Oct 25, 2019

Read reciept for messages #4957

Closed

This was referenced Nov 22, 2019

read receipts? #3411

Closed

[NEW] Message read receipts #9717

Merged

wreiske mentioned this issue Apr 29, 2021

Read receipts are broken....again #21861

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Read receipts not working #15484

Read receipts not working #15484

phriedrich commented Oct 2, 2019

robopossum commented Oct 2, 2019

Yures commented Oct 2, 2019 via email

dca-adam commented Oct 3, 2019

johnbrown-yoti commented Oct 3, 2019

gennari-dkt commented Oct 8, 2019

bkraul commented Oct 9, 2019 •

edited

Loading

reetp commented Oct 15, 2019

geekgonecrazy commented Oct 16, 2019

wreiske commented Oct 16, 2019 •

edited

Loading

bkraul commented Oct 16, 2019 •

edited

Loading

wreiske commented Oct 16, 2019 •

edited

Loading

bkraul commented Oct 16, 2019

phriedrich commented Oct 17, 2019

wreiske commented Oct 22, 2019 •

edited

Loading

reetp commented Oct 22, 2019

Wirone commented Oct 23, 2019

rodrigok commented Oct 23, 2019

wreiske commented Oct 23, 2019

rodrigok commented Oct 23, 2019

GoetheG commented Nov 22, 2019

gerroon commented Apr 25, 2020

kgdemir commented Sep 15, 2020 •

edited

Loading

phriedrich commented Sep 15, 2020

Read receipts not working #15484

Read receipts not working #15484

Comments

phriedrich commented Oct 2, 2019

Description:

Steps to reproduce:

Expected behavior:

Actual behavior:

Server Setup Information:

Additional context

Relevant logs:

robopossum commented Oct 2, 2019

Yures commented Oct 2, 2019 via email

dca-adam commented Oct 3, 2019

johnbrown-yoti commented Oct 3, 2019

gennari-dkt commented Oct 8, 2019

bkraul commented Oct 9, 2019 • edited Loading

reetp commented Oct 15, 2019

geekgonecrazy commented Oct 16, 2019

wreiske commented Oct 16, 2019 • edited Loading

bkraul commented Oct 16, 2019 • edited Loading

wreiske commented Oct 16, 2019 • edited Loading

bkraul commented Oct 16, 2019

phriedrich commented Oct 17, 2019

wreiske commented Oct 22, 2019 • edited Loading

reetp commented Oct 22, 2019

Wirone commented Oct 23, 2019

rodrigok commented Oct 23, 2019

wreiske commented Oct 23, 2019

rodrigok commented Oct 23, 2019

GoetheG commented Nov 22, 2019

gerroon commented Apr 25, 2020

kgdemir commented Sep 15, 2020 • edited Loading

phriedrich commented Sep 15, 2020

bkraul commented Oct 9, 2019 •

edited

Loading

wreiske commented Oct 16, 2019 •

edited

Loading

bkraul commented Oct 16, 2019 •

edited

Loading

wreiske commented Oct 16, 2019 •

edited

Loading

wreiske commented Oct 22, 2019 •

edited

Loading

kgdemir commented Sep 15, 2020 •

edited

Loading