From 30250216e8f8ee19638cddfeb1a9a22476d851a3 Mon Sep 17 00:00:00 2001 From: levlam Date: Fri, 18 Oct 2019 15:57:16 +0300 Subject: [PATCH] Never log updateReadHistoryInbox with 0 max_message_id. GitOrigin-RevId: f4b3ca895e39f55318054268329d26b7932e41c3 --- td/telegram/MessagesManager.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/td/telegram/MessagesManager.cpp b/td/telegram/MessagesManager.cpp index 39f72c628..212376834 100644 --- a/td/telegram/MessagesManager.cpp +++ b/td/telegram/MessagesManager.cpp @@ -8462,7 +8462,8 @@ void MessagesManager::read_history_inbox(DialogId dialog_id, MessageId max_messa Dialog *d = get_dialog_force(dialog_id); if (d != nullptr) { - if (!max_message_id.is_valid() && (max_message_id != MessageId() || d->last_read_inbox_message_id != MessageId())) { + // there can be updateReadHistoryInbox up to message 0, if messages where read and then all messages where deleted + if (!max_message_id.is_valid() && max_message_id != MessageId()) { LOG(ERROR) << "Receive read inbox update in " << dialog_id << " up to " << max_message_id << " from " << source; return; }