From 3dc2716ee24c878a342f12ffec9189aa7aa48027 Mon Sep 17 00:00:00 2001
From: levlam <levlam@telegram.org>
Date: Fri, 18 Oct 2019 17:43:31 +0300
Subject: [PATCH] Drop invalid last_new_message_id.

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

diff --git a/td/telegram/MessagesManager.cpp b/td/telegram/MessagesManager.cpp
index dce2d5a39..a329b9bcc 100644
--- a/td/telegram/MessagesManager.cpp
+++ b/td/telegram/MessagesManager.cpp
@@ -25052,6 +25052,10 @@ void MessagesManager::fix_new_dialog(Dialog *d, unique_ptr<Message> &&last_datab
     last_message_id = last_database_message_id;
   }
 
+  if (!d->last_new_message_id.is_valid() && d->last_new_message_id != MessageId()) {
+    LOG(ERROR) << "Drop invalid last_new_message_id " << d->last_new_message_id << " in " << dialog_id;
+    d->last_new_message_id = MessageId();
+  }
   if (!d->last_new_message_id.is_valid() && d->max_unavailable_message_id.is_valid() &&
       d->max_unavailable_message_id.is_server()) {
     LOG(ERROR) << "Bugfixing wrong last_new_message_id with max_unavailable_message_id to "