fix: update last notified correctly, notification delay (WPB-22701) #4548
+18
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



https://wearezeta.atlassian.net/browse/WPB-22701
https://wearezeta.atlassian.net/browse/WPB-22701
What's new in this PR?
Issues
Application was not showing all notification when receiving a lot of messages.
Causes (Optional)
Messages for notifications are queried from the
Messagestable based on the message timestamp and conversationlast_notified_date. Last notified date was not updated correctly and some messages were filtered out by query.Notification updates are based on the
activeNotificationsproperty ofNotificationManager. New notifications for same conversation are combined with already shown notifications. When multiple notifications are shown very fastactiveNotificationsproperty does not always have up-to-date list of notifications. This is causing incorrect updates based on out-of-date list.Solutions
activeNotifications.