It was a BlueBox issue. If I desabled the BlueBox by sfsClient.setUseBlueBox(false); It works well.

I am still testing the Android API 1.0.1 and I got more problems. When I tried to connect to server with the wifi desabled, I got a CONNECTION_LOST event. It's expected and good. But the SmartFox connecting thread seems kept running!!! If I try to invoke SmartFox#connect() again, I got nothing. No C...

I am from China. It's really difficult for me to access the online api document for...some reason...known as GFW. I need an offline api document package. Is there something like that?

For now, I think write a heart beat thread is still the best way to resolve this. Since even the client can catch the disconnect event, the server can't notice the user disconnected.

If we could listen OnDisconnect event. It would be cool, even better than CONNECTION_LOST event. But I haven't found a way to listen that event.

If the API version causing the issue is the one contained in the example package, this is normal because we don't recompile and update the packages each time a new version of the API is released. In fact in the tutorials we clearly recommend to get the latest API available. I think both libs in exa...

It seems a build configuration issue. I built the apk with libs downloads from android API package here http://www.smartfoxserver.com/download/sfs2x#p=updates . After I override the libs with the files in the example pack it works well. I am still confused. Since the change log of android client API...

I am running the Tris example on android. It works well until I want to test the CONNECTION_LOST event handling. After logined the server, I disabled wifi from android setting, so the connection should be broken. I was expecting a CONNECTION_LOST event but nothing happened. I also tried this in Tris...