You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I started seeing following error in log:
While deserializing vector<%Message>: WTelegram.WTException: Cannot find type for ctor #94f592db at TL.Serialization.ReadTLObject(BinaryReader reader, UInt32 ctorNb) at TL.Serialization.ReadTLDictionary[T](BinaryReader reader) at TL.Serialization.ReadTLObject(BinaryReader reader, UInt32 ctorNb) at WTelegram.Client.ReadMsgContainer(BinaryReader reader)
Connection takes much longer now, but eventually succeeds.
I am at v 3.5.3. Updating to the latest 3.5.6 did not fix it. - there are no relevant changes there anyway.
It looks like a valid ctor based on this: https://github.com/laganovskaakarina/schemas/blob/master/TL_telegram_v164.tl
though I admittedly know little about mechanics under the hood to troubleshoot it. Though I'd let you know in case it is something worth looking at.
Your work is remarkable and much appreciated.
The text was updated successfully, but these errors were encountered:
Such errors may happen initially (right after LoginUserIfNeeded) when you just updated (or downgraded) your version of WTelegramClient. (this is because old updates based on previous version of the API layer have accumulated while your client was stopped)
In which case, some errors like this may show up ONLY in the logs and WTelegramClient should be able to ignore the errors and continue execution normally (no exceptions raised). After the initial batch of updates, that error should not show up again.
Keep me informed if you still see this error (for that user account), or if it no longer happens.
Today I started seeing following error in log:
While deserializing vector<%Message>: WTelegram.WTException: Cannot find type for ctor #94f592db at TL.Serialization.ReadTLObject(BinaryReader reader, UInt32 ctorNb) at TL.Serialization.ReadTLDictionary[T](BinaryReader reader) at TL.Serialization.ReadTLObject(BinaryReader reader, UInt32 ctorNb) at WTelegram.Client.ReadMsgContainer(BinaryReader reader)
Connection takes much longer now, but eventually succeeds.
I am at v 3.5.3. Updating to the latest 3.5.6 did not fix it. - there are no relevant changes there anyway.
It looks like a valid ctor based on this: https://github.com/laganovskaakarina/schemas/blob/master/TL_telegram_v164.tl
though I admittedly know little about mechanics under the hood to troubleshoot it. Though I'd let you know in case it is something worth looking at.
Your work is remarkable and much appreciated.
The text was updated successfully, but these errors were encountered: