Impossible to mark conversation as read

Describe your environment

• Device model: Samsung Galaxy Tab S5e SM-T720
• Android version: 11
• What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847

Steps to reproduce

• Can you reproduce the bug: at will (but only with these accounts)
• Steps:
  1. Open an unread conversation
  2. The conversation is mark as read
  3. Close the app and reopen
• Actual result: The same conversation reappears unread

Additional information

output

created branch 1206-impossible-to-mark-as-read to address this issue

changed the description

changed title from Impossible to mark as read to Impossible to mark conversation as read

For info, I have all these accounts connected to my device.

added bug + 1 deleted label

removed 1 deleted label

added BacklogMedium label

Scenario suggested by @sblin:

• Send a message from Bob into a swarm group
• Alice into this swarm should see a message notification
• Bob add a third person

Expected result:

• Alice should be able to mark notification as read

Actual result:

• Alice can't mark notification as read

added to epic &66 (closed)

marked this issue as blocked by #1494 (closed)

marked this issue as related to #1522 (closed)

mentioned in issue #1522 (closed)

assigned to @alussier-cullen

added SprintTo review label

Fix is made but it seems to me like there is further work that could be done to better unify the way all clients handle the mark as read status.

removed SprintTo review label

closed

reopened

added SprintTo review label

still in review https://review.jami.net/c/jami-client-android/+/27246

There seems to be larger problems with the tracking of last seen messages at the daemon level as it affects all client when "special" messages like conversation joins are involved.

removed SprintTo review label

unassigned @alussier-cullen

closed

reopened

added smartlist label

added natureintermittent label

added sprintbacklog label

removed from epic &66 (closed)

added to epic &69