Page 2 of 2
Posted: 30 Aug 2010, 21:40
by dingo
actually i get the same error on firefox mac once in a while, i never really cared because i just continue the debugger and everything works fine.
perhaps it has something to do with the fact that the debugger has a socket connection too?
Posted: 31 Aug 2010, 14:30
by fardeen
Thanks shvilam.
This issue occurs also on the non debugger version unfortunately.
What i been told that it is a syc problem
Posted: 31 Aug 2010, 15:04
by shvilam
That same of things happen in a different sync
I also can reporter that I am now running Ubuntu and chrome and the game working fine
i am not running the debugger version of the flash player here
Keep me update
Posted: 30 Nov 2010, 17:34
by sideDoor
Any updates on this issue?
We are intermittently experiencing the same problem - it also seems to occur while entering the play state of the game: it appears to be Chrome specific, and what appears to be happening is that a message is returned from the SFS via Chrome mal-formed, perhaps causing the unexpected EOF in line 3010 of the SmartFoxClient.as object:
var b:int = socketConnection.readByte()
Any new ideas? As Chrome is now used by 10% of our user-base, it's an issue we must solve!
Thanks, sd.
hope that we will get new replay from Lapo
Posted: 30 Nov 2010, 17:42
by shvilam
hope that we will get new replay from Lapo
Posted: 01 Dec 2010, 08:47
by Lapo
Hi,
can you remind me how to login? Maybe you can send me a PM with an access to the game?
no problem i will send you
Posted: 01 Dec 2010, 09:14
by shvilam
no problem i will send you
Posted: 01 Dec 2010, 10:22
by Lapo
Chrome is my default browser under the Mac. If I login in your website I get
no problem whatsoever.
I tried Chrome running on a Windows 7 PC: no problem again.
Finally I tested on a Windows XP machine where Chrome was not even installed. Downloaded it and installed a brand new copy of it.
Launched your website, everything is cool
I don't think this problem is really so big. Maybe it happens to a small portion of users that run an old Chrome with an old Flash Player, who knows... not easy to find out.
My suggestion: If anyone has problems with Chrome just recommend that they update to the latest version. This should also ensure that they use the latest Flash Player.
Hope it helps
Thanks again i haven't test this myself for a long time
Posted: 01 Dec 2010, 11:13
by shvilam
and i can confirm as you said that under windows 7 and running the latest version of chrome is running fine
Posted: 01 Dec 2010, 17:56
by fardeen
We have 5000 people getting this issue per day so i can confirm that there is a bug with chrome PC (not Mac) and SFS Client.
Our QA needs to test hundred games to get the error once. That why this error is so difficult to resolve.
Telling us that it's working on your side is not helping at all... We paid for SFS and we were expecting a better support...
Posted: 02 Dec 2010, 08:38
by Lapo
@fardeen
I think there is a misunderstanding here, Let me make this clear:
1) We don't exclude the possibility that a problem existed with older versions of Chrome but the problem lies down deep in the guts of Chrome itself. We don't have any control over these types of bug.
Out API use the Socket class from the Flash framework. If a bug exists in the implementation of sockets in Chrome, we have absolutely no control over this. Do you understand? We are in the same situation as you are.
2) We have tested the latest versions of Chrome to see the problem in action and the result is that no problem was found! Additionally other users reported the same thing. Well this is a very good news. It means that the latest edition of Chrome has finally fixed the issue. Nice job, Google!
With this said the solution is quite simple. Make sure to clearly state in your website, in the support pages etc... that if any User encounters a problem with Chrome they should please immediately upgrade to the latest version.
Hope it helps