Socket.io v1.x with native platform

thomasjab · June 8, 2015, 11:47am

Hello,

i’m working on multiplayer game with socket.io/nodejs server and cocos2d-js 3.6.1 as client.
Everything works with socket.io v0.9x but not with 1.x (400 transport error).

I have manually changed socket.io.min.js in cocos2d html5 and server to 1.x. It works. But it does not work for native version.

I see some post talking about socket.io v0.9x and v1x support with cocos2d-x. Do you know how to support socket.io 1.x on native platform with cocos2djs ?

Thanks

pandamicro · June 9, 2015, 5:00am

In fact, the socket io native implementation need to be upgraded, sorry for the inconvenient. It’s scheduled to v3.8:
https://github.com/cocos2d/cocos2d-x/issues/11739

The current implementation is here: https://github.com/cocos2d/cocos2d-x/blob/v3/cocos/network/SocketIO.cpp

thomasjab · June 9, 2015, 6:18am

Thank you @pandamicro

StudioAMK · September 15, 2015, 8:16pm

@pandamicro

Has this fixed?
Thanks

StudioAMK · September 16, 2015, 8:20am

With 3.8, I could connect but, emit didnt work. Help please… . @pandamicro

On Android… HTML worked fine.

StudioAMK · September 16, 2015, 4:12pm

@thomasjab Did you managed to solve socket.io issue? Thanks

StudioAMK · September 16, 2015, 8:05pm

Reporting:

Continuing the discussion from Socket.IO Extention Update - 1.x working with 0.9.x backwards compat:

Socket.IO Extention Update - 1.x working with 0.9.x backwards compat

This is the server script. It sends “Hello” upon a new socket connected and has another listener “rpc”.
That “rpc” listener sends “rpc_ret” to client.

<img src="/uploads/default/10796/e5cb2510e19230e0.PNG" width=“690” height=“443”>

Here’s client script

<img src="/uploads/default/10797/7fd27fb69af22736.PNG" width=“690” height=“491”>

Upon the client connects, it emits a “rpc” message with a data object.

Here’re the test results:
First tested on Browser and resulted as desire (logs from console):

<img src="/uploads/default/10798/fe8a4546459aa8df.PNG" width=“687” height=“110”>

The was from NodeJS. The request from browser was successfully logged.

<img src="/uploads/default/10799/46a6dcd514b2de6a.PNG" width=“569” height=“51”>

And then, complied, sync the apk from adb and ran the app.
Here’re the logs from logcat:

<img src="/uploads/default/10800/45e4cbbf95b85f04.PNG" width=“580” height=“500”>

<img src="/uploads/default/10801/dd581bde8566691d.PNG" width=“684” height=“257”>

There were warnings:
09-17 00:35:13.634: W/dalvikvm(17476): dvmFindClassByName rejecting 'org/cocos2dx/lib/Cocos2dxLocalStorage'
09-17 00:35:43.374: W/dalvikvm(17476): dvmFindClassByName rejecting 'org/cocos2dx/lib/Cocos2dxHttpURLConnection'
Not sure they were the causes. Nonetheless, from the log, I learnt that object can’t be sent as parameter. So, I modified my codes to send as string.

Client Script (before sending to server:)
<img src="/uploads/default/10802/c3abcb9ebd7b874c.PNG" width=“292” height=“48”>

Then, compiled and tested again
<img src="/uploads/default/10803/65f2919a1afdff27.PNG" width=“682” height=“447”>

Emit was called without error now. But, server didn’t receive any call. I also noticed there were several onMessage calls in the Android log. So, I thought, server was sending the calls.

So, I modified server codes again to log before sending “hello”. Then I found out that server was not sending the “hello” calls. Other than replys to “rpc” calls with “rpc_ret”. So, I think, “rpc_ret” calls were being replaced by previous “hello” call. I think, they were mixed up somehow somewhere.

I don’t know how to continue as I ran out of ideas.
Perhaps, if you have working sample that you can share with, I’d be glad to have it and learn from it.

Thanks in advance again… T.T

Hope you can help me… @hannon235…

@lambda… @pandamicro… . Could you please help me too?

thomasjab · September 17, 2015, 11:03am

I switched to websocket. I don’t know if native platform have been updated

hannon235 · September 17, 2015, 4:29pm

Cross posted from Socket.IO Extention Update - 1.x working with 0.9.x backwards compat , let’s keep the discussion in this thread

@StudioAMK Is this only happening on Android, or can you test the same code on Win32 or OSX? If the issue is only on Android, are you enabling permissions for local storage and network access in your Android Manifest XML file?

This could be the cause of both warnings about storage and http classes, as well as the reason that the code works without error but no network packets are sent.

StudioAMK · September 17, 2015, 10:35pm

@hannon235

Edit: Just tested on Win32. Same issue. Incoming ok. Outgoing failed.

what I got form AndroidManifest.xml (looks ok?):

<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE"/>  
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE"/>  
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>  
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>  

<uses-permission android:name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

Beside that, I’ve compiled and tested with Cocos2d-X JS test project yesterday. The same issue.

Could this be because of NDK / SDK / JDK versions?

StudioAMK · September 17, 2015, 10:36pm

Source Codes Added There:

hannon235 · September 20, 2015, 12:57am

fixed in https://github.com/cocos2d/cocos2d-x/pull/13953

agriz · March 11, 2016, 1:56pm

If we use socket.io.js from socket.io, will it work in android and ios?