Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] - Messages remain unread in Axolotl #172

Open
AA303 opened this issue Sep 7, 2020 · 4 comments
Open

[BUG] - Messages remain unread in Axolotl #172

AA303 opened this issue Sep 7, 2020 · 4 comments
Labels
Milestone

Comments

@AA303
Copy link

AA303 commented Sep 7, 2020

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
Copy link
Collaborator

nanu-c commented Sep 7, 2020

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
Copy link
Collaborator

nanu-c commented Sep 28, 2020

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

@nanu-c nanu-c closed this as completed Sep 28, 2020
@AA303
Copy link
Author

AA303 commented Dec 8, 2020

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
Copy link
Collaborator

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

@Flaburgan Flaburgan reopened this Dec 9, 2020
@Flaburgan Flaburgan added the bug label Jan 12, 2021
@Flaburgan Flaburgan added this to the 1.0.0 milestone Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants