Notifications about previous messages should disappear when chat is opened

[lukaszfryc]

Description

Type: Bug

Summary: Let's say you have 3 notifications about messages for one chat. When the last notification is clicked which opens the chat. Now, the previous 2 notifications should probably be dismissed. The messages were already seen by the user. Instead, user needs to handle the notifications by herself.

Ideally we should dismiss only notifications of messages that we are sure have been seen by the user. It may happen that there is some old message that user needs to scroll to see. But, the simple solution is to dismiss all related notifications when the chat is opened. I think it's much better than seeing 10 other notifications of a chat that was already seen (the case right now).

Expected behavior

Dismiss notifications when a chat was seen.

Actual behavior

Chat notifications stay even though the messages were seen.

Reproduction

• User 1: Open Status
• User 2: Keep Status app in the background
• User 1: Send 2 messages to User 2
• User 2: Click on the first message and open the chat with User 1
  -> 2nd notification is still visible.

Additional Information

• Status version: nightly, March 1
• Operating System: iOS, Android

[lukaszfryc]

It was not fixed by #86 nor #119

@pombeirp are you aware of any swarm that can fix it?

[pedropombeiro]

@lukaszfryc https://github.com/status-im/ideas/blob/master/ideas/86-push-notif-v2.md is still in draft mode (it was closed in favor of a pull request to add a Markdown file). It should start soon.

GitHub

status-im/ideas

ideas - Swarm Home. New, completed and in-progress features for Status

[lukaszfryc]

Any update on this issue?

[pedropombeiro]

Although this was planned to be fixed in 086-push-notif-v2, there's no reason why work can't start outside that scope. The work that needs to be done is well known (we should send message ID in PN payload (data field), and we should look into dismissing a PN once that message ID appears on screen)

[ghost]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ghost]

This issue has been automatically closed. Please re-open if this issue is important to you.