From 14f1b3cd4b8a4abcd080f0305c9ae015d136d75a Mon Sep 17 00:00:00 2001
From: levlam <levlam@telegram.org>
Date: Fri, 6 Dec 2019 22:49:07 +0300
Subject: [PATCH] Always ignore updateReadHistoryInbox.still_unread_count,
 because it can be wrong even in updates.

GitOrigin-RevId: ff2222911c995605d813a942ccf833b7e7d620bb
---
 td/telegram/MessagesManager.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/td/telegram/MessagesManager.cpp b/td/telegram/MessagesManager.cpp
index 97424e453..aaed841f3 100644
--- a/td/telegram/MessagesManager.cpp
+++ b/td/telegram/MessagesManager.cpp
@@ -6251,8 +6251,8 @@ void MessagesManager::process_update(tl_object_ptr<telegram_api::Update> &&updat
         folder_id = FolderId(read_update->folder_id_);
       }
       on_update_dialog_folder_id(dialog_id, folder_id);
-      read_history_inbox(dialog_id, MessageId(ServerMessageId(read_update->max_id_)), read_update->still_unread_count_,
-                         "updateReadHistoryInbox");
+      read_history_inbox(dialog_id, MessageId(ServerMessageId(read_update->max_id_)),
+                         -1 /*read_update->still_unread_count*/, "updateReadHistoryInbox");
       break;
     }
     case telegram_api::updateReadHistoryOutbox::ID: {