forums.smartfoxserver.com

Hello there:
Here is a issue we met when we trying to use the unity3d with sfs.

We are using the latest plugin, with sfs 2.1.0, when client is disconnected by the server(if the client doing nothing) for idling reason, then we try to connect to the server again,but we found the IsConnected property is still true(but it should be false, because the server have already kicked us out), and the sfs.Connect() is apparently not working (the server didn't get the request message at all),we suspect the Connect() checked the IsConnected property before the does the job, and if it's true, it wouldn't connect for us. and sure we can't get OnConnection event.

This is all what about, and it's all happening to the latest version of the plugin, we tested the old one, and it is working.

I am just trying to confirm if it's a approved bug, or it's just my own issue. If it is a bug, when do you think it can be fixed? Maybe next update? When will next update be released? It's really difficult to find another way around this issue for our project.

Looking forward your feedback, thanks.

I am having the same issue.
we are not using bb, and it turns out the plugin got this re-connect problem, seens as long as u r disconnected by the server, you will have trouble to connect again ( because plugin always result true from IsConnected property, it wouldn't alow the Connect() work).
is there any alternative way to get this work? or of course get it fixed.

There is a fix underway for this.

Turns out that there is a Mono bug where the socket never stops listening if the server disconnects (e.g. via kick). Documentation and whats happening doesnt correlate.

So doing something else, but its slightly complicated (and annoying to have to code around low level Mono bugs) and needs much more testing before its released.

For now there is no workaround identified - other than dont kick connections from server :-/

/T

Hi Thomas,

This issue is also bothering me, I hope you will be able to repair it. How is the fix coming along?

You probably already know this, but just to be sure: although IsConnected stays true when kicked from the server, the CONNECTION_LOST event does fire on the client side. So there is something on the client side that is noticing the disconnect. I don't know if this is on the socket level or higher, but I hope this is something you can use

Regards,

Micr0mega

This should be fixed in the 1.0.3 release of the API.

If not, hit me with a bat!

/T

*gets out the nerf bat*

It would seem this bug was re-introduced with client API release 1.0.4.
Also, after importing the new library into my assets, it makes my Unity editor (version 3.5.6) lock up when leaving "play mode" of a scene.
I switched between 1.0.3 and 1.0.4 a few times to verify both behaviors and described issues only occur with 1.0.4.

The DLL from the 1.0.4 zip file reads 1.0.2.0 in its version tab (Windows Explorer properties), though it has a different size and content from version 1.0.2 (and 1.0.3 for that matter). Could it be that the code for 1.0.4 was erroneously based on 1.0.2 instead of 1.0.3?

*stops batting Thomas*

There, that should be just enough to keep you sane to look into this, shouldn't it? This update is a "downdate" for me.

Hmmm,

Thats weird. We are running 3.5.6 in the studio and no one has complained (and trust me - they would). Then again we are running SVN version, so if there has been a mistake with the build machine not having been 100% up to date on 1.0.3 then you would run something different than us.

Hit me up with a PM including your email - and I'll send you a fresh build and lets take a look!

/Thomas