Error: Could not find a matching Constructor ID about telegram-tt

[Ajaxy]

Hi there. Thanks for the report. Do you know how to reproduce it?

[painor]

[ERROR] - [Unhandled error while receiving data]
[ERROR] - [Error: Could not find a matching Constructor ID for the TLObject that was supposed to be
        read with ID 253890367. Most likely, a TLObject was trying to be read when
         it should not be read. Remaining bytes: 480]

This error needs to be handled, because it can cause very serious problems in some places (e.g. chat list or message history not being loaded).

Fun fact: this error also often happens in Telethon, which GramJS is based on.

ID 253890367(which is f220f3f in hex) belongs to https://core.telegram.org/constructor/userFull in layer 105. Telegram sometimes returns data for the wrong layer and there isn't much we can do about since we don't save all past layers only the most recent one.

[ingria]

Do you know how to reproduce it?

@Ajaxy no, it just happens randomly. I couldn't find any way to reproduce it.

ID 253890367(which is f220f3f in hex) belongs to userFull in layer 105.

@painor This error can happen with any constructor, not just this one.

Telegram sometimes returns data for the wrong layer and there isn't much we can do about

Yep, that's why it's necessary to catch this type of error and handle it somehow. Right now it can render the app unusable.

[Ajaxy]

Right now it can render the app unusable.

What does exactly happen? Do you have a screenshot?

[ingria]

For example, this error may cause infinite archived chats loading:

The only way to open archived chats in that case is to reload the page.

[Ajaxy]

Fixed in cf2db92.