Skip to content

fix: Emit MsgsChanged instead of MsgsNoticed on self-MDN if chat still has fresh messages #7741

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.

Sign up for GitHub

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

Merged
iequidoo merged 1 commit into from
Jan 20, 2026
Merged

fix: Emit MsgsChanged instead of MsgsNoticed on self-MDN if chat still has fresh messages #7741

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions src/receive_imf.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1017,12 +1017,12 @@ UPDATE msgs SET state=? WHERE
)
.await
.context("UPDATE msgs.state")?;
// Removes all notifications for the chat in UIs. Ideally should be under
// `if chat_id.get_fresh_msg_cnt(context).await? == 0`, but this causes a not
// updated profile badge counter in the UIs as of v2.35.0. Removed notifications for
// new messages is an already existing and known problem, so let's emit the event
// unconditionally for now.
context.emit_event(EventType::MsgsNoticed(chat_id));
if chat_id.get_fresh_msg_cnt(context).await? == 0 {
// Removes all notifications for the chat in UIs.
context.emit_event(EventType::MsgsNoticed(chat_id));
} else {
context.emit_msgs_changed_without_msg_id(chat_id);
}
chatlist_events::emit_chatlist_item_changed(context, chat_id);
}
if archived_chats_maybe_noticed {
Expand Down