search

axolotl-chat / axolotl

A Signal compatible cross plattform client written in Go, Rust and Vuejs
https://axolotl.chat
GNU General Public License v3.0
326 stars 52 forks source link

[BUG] - Messages remain unread in Axolotl #172

Open AA303 opened 4 years ago

AA303 commented 4 years ago

Description

Messages remain unread in Axolotl even after they are read in the desktop client.

Steps to Reproduce

  1. As a sender to send you a message and read it on the desktop client

Expected behavior: [What you expect to happen]

The message should be marked as read in Axolotl chat list.

Actual behavior: [What actually happens]

The message remains unread in Axolotl, until you open the chat.

Versions

0.8.7 Please provide the Version as written in Settings->Advanced-> Submit Debug Log

Device

Nexus 5

Link to Debug Log

Please provide a link to debug

nanu-c commented 4 years ago

The ticks in axolotl only show:

  1. tick, successful sent to signal server.
  2. tick the signal server acknowledge the message. That's only triggered, when sending messages from axolotl. I could lie and always but 2 ticks if they are sent from signal desktop. Or properly implement message read messages...
nanu-c commented 4 years ago

duplicate of #91 and it's going to be solved

AA303 commented 3 years ago

I have upgraded to 0.9.0 the issue is not resolved. When I read entire conversation on linked Desktop Client - the Axolotl still displays unread counter on the list of conversations.

The issue with two ticks is a different issues - which is working great in 0.9.0.

Flaburgan commented 3 years ago

Yes, this is indeed not related to ticks and is still a problem, I'm reopening.