-
Notifications
You must be signed in to change notification settings - Fork 3k
"Invalid UTF-8 detected" since switch to socket.io 1.0 #671
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
Comments
+1 exactly the same scenario. Any information about this? |
For me it fails at """utf8decode""" with byteString
|
Thanks for reporting @Canop, @JGAntunes and @dunice-valentin. We fixed a UTF-8 problem in 1.0.3 recently. Could you give 1.0.3 a try? Let me know how it goes! If that doesn't do it for you, would it be possible to get a server and client code snippet to reproduce the problem with? Thanks! |
@rase- 30 mins of development. All looks fine. |
@dunice-valentin ok, thanks! Let me know if something turns up! |
It looks like it works with 1.0.3 (twas a little long to put up because I still have to go around a few things until this gets merged). |
Updated to 1.0.3 but know I've came across a different issue. Waiting for this to be solved so I can test this properly. |
+1 |
1.0.4 solved it to me, thanks @rase- |
decodeSymbol now throws this error which breaks the exchange : "Invalid UTF-8 detected"
I changed nothing to my application which worked in 0.9 and I don't exchange any byte buffer, just plain JavaScript objects.
Is there a way I can get more information on this error ?
The text was updated successfully, but these errors were encountered: