RocketChat / Rocket.Chat

The communications platform that puts data protection first.
https://rocket.chat/
Other
40.4k stars 10.51k forks source link

DM (Direct Message) Often Not Showing Responses Unless We Do CTRL+R #26844

Open volomike opened 2 years ago

volomike commented 2 years ago

Thank you for this sensational product! I have a small bug to report. At least in my tests on the Desktop App, and not when we do group chats, but when we do DMs (Direct Messages) with friends, we're often not seeing responses unless we do a CTRL+R.

This occurred for me on the latest Win 11 and also an updated Lubuntu Linux 20.04.1 LTS with the 5.4.0-122-generic RocketChat/Rocket.Chat.Electron#138-Ubuntu SMP kernel.

The version of the server is: 4.8.3, Apps Engine Version 1.32.0, Node Version v14.18.3, MongoDB 4.2.17.

The version of the desktop app is: 3.8.6.

All default settings.

To reproduce:

  1. Connect to a privately installed Rocket Chat server installed on Linux, using either the Win 11 desktop app or Linux desktop app for Rocket Chat. (This may also occur on Mac -- I haven't tested.)

  2. Click on one of your channels.

  3. In the upper right, click on the Members icon.

  4. Find a member, hover over their icon, and click the vertical ... button.

  5. Choose Direct Message.

  6. Type a message in that DM. You'll see it turn light grey. Using your cellphone or some other means of live communication, ask this person to type a response. Often, you won't see their response when they say they have responded. Give it about 2 more minutes of time and you still won't see a response.

  7. Type CTRL+R to reload everything. You'll now see their response.

The expected behavior was that, at step 6 above, you see a response immediately after they posted it, or at least within 15 seconds of posting it.

jeanfbrito commented 2 years ago

Hello @volomike, did you tested if this happens on the web browser? Because this seems to be an issue on the server side. Electron doesn't touch the channels list. It seems to be a known old issue with the server not propagating the message.

volomike commented 2 years ago

Hello @jeanfbrito . Indeed you are correct. I just tested with the web client and it works just fine. It's only the Electron app with the issue. This is leading me to believe that it's a Desktop app bug.

jeanfbrito commented 2 years ago

Could you click on the menu View -> Open Devtools and see if there is any errors on the console tab?

It's very weird to be an issue on the desktop app for this kind of stuff. Then I will need your help to track this bug.

Could you try if this happens on the server open.rocket.chat too? Just to see if is just with your server.

volomike commented 2 years ago

Here's a screenshot of Dev Tools for us. Note, I typed a DM and got an immediate response this time. Weird! So, it's an intermittent issue I guess. However, I had the Desktop app open on both Windows and Linux, and also had the web app open. But all three immediately had the response on this DM.

https://www.screencast.com/t/4nxC71ns0

Unfortunately, I'm a little tied up for time today on client workload to do the open.rocket.chat test and a DM with someone there. I'll try to attempt that on 8/19/2022 and get back to you.

eholloway135 commented 2 years ago

Having a similar issue on all chats, not just dm's using v.3.8.8 Found it affects both the browser and the desktop app so far can only confirm it does it in windows 10 environment. It shows light grey and then you refresh and it shows sent.

jeanfbrito commented 2 years ago

Ok, this is a server issue that is happening then. Did you tried updating the server? I think that I will move it to the server repository but first will wait for your replies.

HrHeun commented 2 years ago

I'm having also this problem on 5.1.1 Maybe related to #26820

I discovered this Bug in the browser and desktop app.

Vaxter commented 2 years ago

Same problem here on 5.1.3 both Electron and in browsers.

GaLaKtIkUs commented 8 months ago

Hello, Any update on this issue? Having the same problem with server 6.6.1 and web client (Chrome 121.0.6167.184 on Linux Fedora 38).