Skip to content

"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

Closed
Canop opened this issue May 29, 2014 · 9 comments
Closed

"Invalid UTF-8 detected" since switch to socket.io 1.0 #671

Canop opened this issue May 29, 2014 · 9 comments

Comments

@Canop
Copy link

Canop commented May 29, 2014

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 ?

@JGAntunes
Copy link

+1 exactly the same scenario.

Any information about this?

@dunice-valentin
Copy link

For me it fails at """utf8decode""" with byteString

byteString
"42["get_finances",{"country":"Ð�Ñ�паниÑ�","stadium":"Ð�м. ЭдÑ�аÑ�да СÑ�Ñ�ового","team_name":"ФÐ� Ð�аÑ�Ñ�елона Ð�адÑ�ид","financal_state":"Ð�огаÑ�","club_state":"Ð�Ñ�оÑ�Ñ�иÑ�ионалÑ�нÑ�й","infrostructure":"Ð�Ñ�Ñ�окий Ñ�Ñ�овенÑ�","manager_account":"10 030 000@","team_cost":"203 000 000@","income_last_week":"400 000@","charges_last_week":"600 000@","profit":"200 000@","profit_state":"positive","salarys":"400 000@"}]���ÿ42["team_stuff:resp",{"stuff":[{"post":"asda","name":"ffdss","skills":"3421","reputation":"sdfsd","age":"28","price":"dfgh"},{"post":"asda2","name""

@rase-
Copy link
Contributor

rase- commented Jun 2, 2014

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!

@dunice-valentin
Copy link

@rase- 30 mins of development. All looks fine.

@rase-
Copy link
Contributor

rase- commented Jun 2, 2014

@dunice-valentin ok, thanks! Let me know if something turns up!

@Canop
Copy link
Author

Canop commented Jun 2, 2014

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).

@JGAntunes
Copy link

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.

@alexiskattan
Copy link

+1

@JGAntunes
Copy link

1.0.4 solved it to me, thanks @rase-

@rauchg rauchg closed this as completed Jun 3, 2014
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

6 participants