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

Error when connect client unable to decode Vector<User>: field Elems: unable to decode UserClass: unexpected id 0x8f97c628 #1166

Open
borzovplus opened this issue Aug 23, 2023 · 8 comments
Labels
bug Something isn't working

Comments

@borzovplus
Copy link

What version of gotd are you using?

0.85.0

Can this issue be reproduced with the latest version?

yes

What did you do?

try connect a lot of clients bot/accounts

What did you expect to see?

no errors

What did you see instead?

rpcDoRequest: unable to decode Vector: field Elems: unable to decode UserClass: unexpected id 0x8f97c628

What Go version and environment are you using?

go 1.20

@borzovplus borzovplus added the bug Something isn't working label Aug 23, 2023
@borzovplus borzovplus changed the title subject: Error when connect client rpcDoRequest: unable to decode Vector<User>: field Elems: unable to decode UserClass: unexpected id 0x8f97c628 Error when connect client rpcDoRequest: unable to decode Vector<User>: field Elems: unable to decode UserClass: unexpected id 0x8f97c628 Aug 23, 2023
@borzovplus borzovplus changed the title Error when connect client rpcDoRequest: unable to decode Vector<User>: field Elems: unable to decode UserClass: unexpected id 0x8f97c628 Error when connect client unable to decode Vector<User>: field Elems: unable to decode UserClass: unexpected id 0x8f97c628 Aug 23, 2023
@borzovplus
Copy link
Author

borzovplus commented Aug 23, 2023

That happened when I upgraded 0.84 to 0.85

@borzovplus
Copy link
Author

0.88 - the same problem

@connorzhuang
Copy link

0.89 - the same problem

@borzovplus
Copy link
Author

0.89 - the same problem

it's happend when there are unread updates after schema upgrading

@guess1122
Copy link

0.90 - the same problem

@guess1122
Copy link

0.89 - the same problem

it's happend when there are unread updates after schema upgrading

Is there any way to solve it?

@scp-66
Copy link

scp-66 commented Dec 11, 2023

I encountered a similar error,It has been bothering me for a long time:unable to decode boxed value:unable to decode MessagesMessagesClass.

@connorzhuang
Copy link

Is there still a solution to this problem that still exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants