Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot find type for ctor #... [after library version upgrade] #191

Closed
dmitry-demchuk opened this issue Sep 29, 2023 · 2 comments
Closed
Labels
duplicate This issue or pull request already exists

Comments

@dmitry-demchuk
Copy link

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.

@PopovNx
Copy link

PopovNx commented Sep 29, 2023

The same problem

@wiz0u
Copy link
Owner

wiz0u commented Sep 30, 2023

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.

@wiz0u wiz0u closed this as completed Sep 30, 2023
@wiz0u wiz0u added the duplicate This issue or pull request already exists label Sep 30, 2023
@wiz0u wiz0u changed the title Cannot find type for ctor #94f592db Cannot find type for ctor #... [after library version upgrade] Oct 1, 2023
@wiz0u wiz0u pinned this issue Oct 1, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants