We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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: parser decode error {type: "TransportError", description: Error: Invalid UTF-8 detected, stack: (...), message: "parser decode error"} description: Error: Invalid UTF-8 detected data: "42["user joined",{"user":{"name":"你好 你去哪儿"},"numUsers":2}]" message: "Invalid UTF-8 detected" stack: (...) get stack: function () { [native code] } set stack: function () { [native code] } proto: d message: "parser decode error" stack: (...) get stack: function () { [native code] } set stack: function () { [native code] } type: "TransportError" proto: d
As about , when i use socket.io , I always get this error at engine.io version 1.5.1 , but if I use version 1.3.1 ,it works. what is the matter?
The text was updated successfully, but these errors were encountered:
It seems your are using old version of engine.io-client. If so, please update it.
Sorry, something went wrong.
No branches or pull requests
Error: parser decode error {type: "TransportError", description: Error: Invalid UTF-8 detected, stack: (...), message: "parser decode error"}
description: Error: Invalid UTF-8 detected
data: "42["user joined",{"user":{"name":"你好 你去哪儿"},"numUsers":2}]"
message: "Invalid UTF-8 detected"
stack: (...)
get stack: function () { [native code] }
set stack: function () { [native code] }
proto: d
message: "parser decode error"
stack: (...)
get stack: function () { [native code] }
set stack: function () { [native code] }
type: "TransportError"
proto: d
As about , when i use socket.io , I always get this error at engine.io version 1.5.1 , but if I use version 1.3.1 ,it works. what is the matter?
The text was updated successfully, but these errors were encountered: