Closed VolodLytvynenko closed 1 month ago
@ajayesivan any update on this?
@cammellos unread-notification count & notification list values coming from status-go API is wrong. I'm looking into the DeleteActivityCenterNotificationForMessage
function in status-go.
still valid and very weird bug (checked on nightly 21/06/24)
so all notifications have the same last-message
and status-go delete notification by matching
to-be-deleted-message-id
with both notification message id
and notification last-message id
code at
for _, notification := range notifications {
if notification.LastMessage != nil && notification.LastMessage.ID == messageID {
withNotification(notification)
}
if notification.Message != nil && notification.Message.ID == messageID {
withNotification(notification)
}
}
last message check is added at https://github.com/status-im/status-go/pull/2854 in order to fix https://github.com/status-im/status-mobile/issues/13933
Steps to reproduce:
User_A
andUser_B
are both in the same community.User_A
sends several replies or mentions toUser_B
.User_A
sends one more message and then deletes it using the 'delete for everyone' option.User_B
checks the AC.Actual result:
All mentions and replies in the AC are removed for
User_B
.Expected result:
Mentions and replies should not be removed from the AC after the last message is deleted.
Additional info:
This issue is similar in group chats, with the exception that only replies are removed from the AC. Mentions are not removed and