Unexpected Unarchiving: Chats Reappear When Searching by Name #26641
Comments
|
for me searching for archived contact name continues to be archived. |
|
@Aokromes Screen.Recording.2023-08-11.at.13.50.12.mov |
|
@Aokromes please investigate this |
|
I have another issue that has remained unanswered. |
|
@Aokromes This is not happening on Android or Telegram Web, only on Telegram Desktop and only on my main account. There are literally no options for this. This seems to be a server-side bug. |
|
I'm not sure they're really unarchived. Maybe they are not loaded at all from the server when you open the app, then you start searching and they are added to the main chats list from the server side search results, because they were not loaded as archived. Can you test it that way - launch Telegram, open Archive and load it down to the very bottom first, then return to All Chats and try reproducing the issue. Will they stay in the list in that case? Or does it reproduce only when the archive wasn't loaded till the bottom? |
|
Hmm, I can't reproduce that way as well. I don't know how this happens :( |
|
Are you sure those contacts were archived? Judging by the video at the moment of searching this contact was in contacts list, but this history wasn't loaded yet (wasn't loaded in all chats or in archive, at all -- no last message):
Then it was loaded from the server side with a server-side search request:
And after that it appeared in the main chats list. Is it possible that this chat wasn't archived at all? What happens if you right click on it in the "All Chats"? Maybe this chat's last message is old enough (not in the last ~500'000 of your messages) and it isn't returned in the main chats list at all, but it is returned when it is requested separately in the search results. |
|
Ok, is it possible that this contact was never archived? You archived all your chats from the main list, but this chat was not in the chats list, it appears there only when it is loaded (using search or opening the message history with that contact). If you archive it and relaunch the app and search like that again -- is it still placed in the All Chats or in archive like it should? |
@john-preston I did the exact thing. Those chats are archived. I have archived them multiple times when they appear. It's strange that this issue only occurs in my main account and not the others. Additionally, it only happens on my desktop, not on my main account on my phone or even Telegram Web.I mean, at the same time, they are in my "All Chats" folder. However, I can't see them on my phone; only on Telegram Desktop.
Yes, I am totally sure.
They had been definitely archived. I tried multiple times myself.
It will act like a normal, unarchived chat.
This is a pretty good guess because in all of my attempts, only those appeared that I hadn't contacted with them for more than a year.
This is not possible.
Just tried that, but there are still the same results. However, there's something strange. When I search their names and then right-click on them, I don't see the "Unarchive" button. Instead, I see "Archive." So it seems they never get archived. I've tried archiving them multiple times, but it appears that the "Archive" command has no effect on them.
Yes, they will appear again. |
|
Ok, we can try debugging it with logs. You can contact me at t.me/preston, I'll ask you to enable DebugLogs, reproduce the issue and send me the logs. The logs contain all the network activity of the app and I'll be able to see if server returns wrong data about archive state of those chats or I wrongly interpret them. |
|
@john-preston I just sent a PM to you. Thank you for investigating. |
|
Yes, confirm that this issue has been resolved. I truly appreciate your efforts. |
Steps to reproduce
Search for a name wherever you desire.
Expected behaviour
Contacts will be unarchived. You need to kill the app so you can restore it to its previous state.
Actual behaviour
Contacts will be unarchived.
Operating system
macos 13.5.1
Version of Telegram Desktop
4.8.10
Installation source
Static binary from official website
Crash ID
No response
Logs
The text was updated successfully, but these errors were encountered: