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

An exception occured in the reactor: WTelegram.WTException: Cannot find type for ctor #whatever after upgrading to v4.x #255

Open
13xforever opened this issue May 7, 2024 · 2 comments

Comments

@13xforever
Copy link

In #191 it is stated:

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

But I've tried to upgrade twice from 3.7.2 (first to 4.0, and today to 4.1.1), and all I get are these exceptions and no events being triggered in OnUpdates at all, so basically nothing works, and rolling back eats the events that were received by 4.x client.

full stack trace I get in the logs on new message:

2024-05-07 23:03:55.5380    322 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:03:55Z   
2024-05-07 23:03:55.5380    323 DEBUG [telegram] Received 1 update 
2024-05-07 23:03:55.5380    324 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:03:56.2067    325 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:03:56Z   
2024-05-07 23:03:56.2067    326 DEBUG [telegram] Received 1 update 
2024-05-07 23:03:56.2067    327 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:03:57.9074    328 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:03:57Z   
2024-05-07 23:03:57.9074    329 DEBUG [telegram] Received 1 update 
2024-05-07 23:03:57.9074    330 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:04:02.5773    331 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:04:02Z   
2024-05-07 23:04:02.5773    332 DEBUG [telegram] Received 1 update 
2024-05-07 23:04:02.5773    333 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:04:02.9091    334 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:04:02Z   
2024-05-07 23:04:02.9091    335 DEBUG [telegram] Received 1 update 
2024-05-07 23:04:02.9091    336 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:04:10.2425    337 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:04:10Z   
2024-05-07 23:04:10.2425    338 DEBUG [telegram] Received 1 update 
2024-05-07 23:04:10.2425    339 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:04:16.5337    340 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:04:16Z   
2024-05-07 23:04:16.5337    341 DEBUG [telegram] Received 1 update 
2024-05-07 23:04:16.5337    342 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:04:39.2969    343 DEBUG [spam] 2>Receiving UpdateShort                              2024-05-07 18:04:39Z   
2024-05-07 23:04:39.2969    344 DEBUG [telegram] Received 1 update 
2024-05-07 23:04:39.2969    345 DEBUG [telegram] Ignoring update of type UpdateUserStatus 
2024-05-07 23:04:39.3283    346 FATAL [spam] 2>An exception occured in the reactor: WTelegram.WTException: Cannot find type for ctor #a66c7efc
   at TL.Serialization.ReadTLObject(BinaryReader reader, UInt32 ctorNb)
   at TL.UpdateNewChannelMessage.ReadTL(BinaryReader reader)
   at TL.Serialization.ReadTLObject(BinaryReader reader, UInt32 ctorNb)
   at TL.Serialization.ReadTLValue(BinaryReader reader, Type type)
   at TL.Serialization.ReadTLVector[T](BinaryReader reader)
   at TL.Updates.ReadTL(BinaryReader reader)
   at TL.Serialization.ReadTLObject(BinaryReader reader, UInt32 ctorNb)
   at WTelegram.Client.ReadFrame(Byte[] data, Int32 dataLen)
   at WTelegram.Client.Reactor(Stream stream, CancellationTokenSource cts) 
2024-05-07 23:04:45.3452    347 INFO  [spam] Connecting to 149.154.167.41:443... 
2024-05-07 23:04:45.3566    348 DEBUG [spam] 2>Sending   InvokeWithLayer`1                        #9F99 
2024-05-07 23:04:45.4182    349 DEBUG [spam] 2>Receiving MsgContainer                             2024-05-07 18:04:45Z (svc) 
2024-05-07 23:04:45.4182    350 DEBUG [spam]             → UpdateShort                            2024-05-07 18:03:55Z   
2024-05-07 23:04:45.4182    351 DEBUG [spam]             → UpdateShort                            2024-05-07 18:03:56Z   
2024-05-07 23:04:45.4195    352 DEBUG [spam]             → UpdateShort                            2024-05-07 18:03:57Z   
2024-05-07 23:04:45.4195    353 DEBUG [spam]             → UpdateShort                            2024-05-07 18:04:02Z   
2024-05-07 23:04:45.4195    354 DEBUG [spam]             → UpdateShort                            2024-05-07 18:04:02Z   
2024-05-07 23:04:45.4195    355 DEBUG [spam]             → UpdateShort                            2024-05-07 18:04:10Z   
2024-05-07 23:04:45.4195    356 DEBUG [spam]             → UpdateShort                            2024-05-07 18:04:16Z   
2024-05-07 23:04:45.4195    357 DEBUG [spam]             → UpdateShort                            2024-05-07 18:04:39Z   
2024-05-07 23:04:45.4195    358 DEBUG [spam]             → MsgNewDetailedInfo                     2024-05-07 18:04:45Z (svc)  
2024-05-07 23:04:45.4195    359 DEBUG [spam]             → MsgNewDetailedInfo                     2024-05-07 18:04:45Z (svc)  
2024-05-07 23:04:45.4195    360 DEBUG [spam]             → MsgNewDetailedInfo                     2024-05-07 18:04:45Z (svc)  
2024-05-07 23:04:45.4195    361 DEBUG [spam]             → MsgsAck            
@13xforever 13xforever changed the title An exception occured in the reactor: WTelegram.WTException: Cannot find type for ctor #whatever An exception occured in the reactor: WTelegram.WTException: Cannot find type for ctor #whatever after upgrading to v4.x May 7, 2024
@oscartorres9
Copy link

exact same error! how to fix it, any ideas?

@13xforever
Copy link
Author

13xforever commented May 9, 2024

This issue specifically about OnUpdates not being triggered, for general issue please see pinned #191

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants