WAClient / WALC

An unofficial WhatsApp Desktop client for linux systems.
GNU General Public License v3.0
248 stars 40 forks source link

Repeated historic @Messages in group chat #196

Closed michaelfswann closed 2 years ago

michaelfswann commented 2 years ago

Describe the bug Had back and forth messages in group chat on my phone, non specific IE not @ messages, opened conversation in WALC (already running, conversation not open) to reply from computer, WALC was showing new @ messages which I had previously received and read. They were all from one participant who was not the person who was chatting at the time. It didn't pick any other people's message where they have @'ed me.

WALC Installation Type: Snap

To Reproduce Opened following shutdown & used saved credentials to log back in.

Follow description group chat with old @ message from third party new not at message from second part back and forth on phone while WALC open on pc on different conversation. Open conversation WALC.

Expected behavior I did not expect to be shown historic and read @ Messages. That were previously not there in same session on PC.

Did you try closing and then opening it back?: / No

System Information (please complete the following information):

Additional context

Is this on a server? No
Do you have multiple clients on the same IP? Potentially as proxy
Are you using a proxy? Yes
Zzombiee2361 commented 2 years ago

Hiya, I don't quite understand the problem. But before we go any further, I just want to let you know that the snap version is currently unmaintained. Please try the latest appimage version to see if the problem persist

michaelfswann commented 2 years ago

Hey ok will do, feel free to mark as solved for now will reopen if it occurs again :) thanks

Sent from my iPhone

On 28 May 2022, at 05:06, Daffa Mumtaz @.***> wrote:

 Hiya, I don't quite understand the problem. But before we go any further, I just want to let you know that the snap version is currently unmaintained. Please try the latest appimage version to see if the problem persist

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

Zzombiee2361 commented 2 years ago

Let me know if it's still happening