Socket-io-v2 WebGL | Firesplash Entertainment | Page 1

wind flame Feb 27, 2023, 11:27 AM

#

Hi
Is there some kind of demo of this asset? Or is there refund option - I need just to confirm, if this will be working with current solution. We have SocketIo v2 library working on mobile, but need to switch to other, to works on WebGL.
https://assetstore.unity.com/packages/tools/network/socket-io-v2-client-for-unity-standalone-webgl-186263?aid=1100lJ2z&utm_campaign=unity_affiliate&utm_medium=affiliate&utm_source=partnerize-linkmaker

terse wadi Feb 27, 2023, 8:36 PM

#

Hi, there is no demo available. What implementation / library are you using on the server side?

Also are you using any "special" features - I mean namespaces, binary messages, ...?

#

📎 Documentation.pdf

#

Also this excerpt from our v3/v4 asset might help. It contains a feature comparison between our three socket.io assets:
https://unityassets.firesplash-entertainment.com/socketio-v4/documentation/#feature-matrix

wind flame Feb 27, 2023, 8:43 PM

#

Yes, namespaces. Is there a workaround for this lack of functionality in this asset?

terse wadi Feb 27, 2023, 8:44 PM

#

not without major code changes unfortunately. This is one of the reasons, why the V4 PLUS asset has a completely new code base

#

(its a complete rewrite)

wind flame Feb 27, 2023, 8:46 PM

#

In this matrix I see that basic namspaces are present.
Btw I need soketIo v2 because our Be uses v2

terse wadi Feb 27, 2023, 8:47 PM

#

basic namespaces?

To be clear: Only emits sent on the default namespace (/) work. Any other namespace is not possible without code changes

#

Please do not mix up namespaces and the "path"

#

.../socket.io/ is the path - "/" is the namespace used if no namespace is explicitely specified (namespaces: https://socket.io/docs/v2/namespaces/ )

Namespaces | Socket.IO

A Namespace is a communication channel that allows you to split the logic of your application over a single shared connection.

wind flame Feb 27, 2023, 8:48 PM

#

Ok. Thx.
We use this on the serverside
https://github.com/mrniko/netty-socketio

#

Ohh. Probably we dont use namespaces. 🙂

#

Anyway I have already bought this asset and I will try it tomorrow. 🙂

terse wadi Feb 27, 2023, 8:51 PM

#

Got no experience with Java and socket.io at all and no reports yet, too. From the first look, the library looks quite full featured and okay.

I'd love to hear your results. If you struggling, ask away, if it's just a small change required, I'll be happy to help - Just major rewrites are out of scope 🙂

wind flame Feb 28, 2023, 7:51 PM

#

Hi again 🙂
I am in the half way of implementation, and looks promising.
however, could you please tell me, what could be a reason for an error: "Disconnected transport error"?

I am trying to implement like in example (which works fine), but this error occurs in the beginning after connecting.

wind flame Mar 1, 2023, 3:39 PM

#

Hi @terse wadi
Please don't bother with previous question.
Instead, could you please tell me, why in Unity Editor it works fine, but in the WebGL build changing address doesn't occur?
I have checkboxes: auto-connect and reconnect disabled, and doing Connect after changing address. Is there any additional step for WebGL? It seems that in WebGL build it somehow 'remembers' addres from inspector on the prefab.
_socketClient.socketIOAddress = "myApp-dev.company.pl/socket.io?auth-token=" + _authorizationToken; _socketClient.Instance.Connect();

wind flame Mar 1, 2023, 4:35 PM

#

In browser console I can see 'Connecting SIO to ..." happens before my address change and my Connect() (both marked in red with Debug.LogError())

wind flame Mar 1, 2023, 4:55 PM

#

Let say I somehow changed address in runtime - but two clients can't receive socket messages (it works in Unity Editor, on two different computers, but doesn't work in browser with WebGL).
I have log: object SocketClient(Clone) does not have receiver for function RaiseSIOEvent!

terse wadi Mar 1, 2023, 5:00 PM

#

wind flame In browser console I can see 'Connecting SIO to ..." happens before my address c...

will check this first, then come back to the other issues.

v2 Asset, right?

wind flame Mar 1, 2023, 5:00 PM

#

yes

#

I think it is something wrong with my implementation, but please give a hint 🙂

terse wadi Mar 1, 2023, 5:03 PM

#

Can you please send a screenshot of the component in the inspector when you got this connections issue? (you can remove the address)

#

just want to make sure we have the same settings

wind flame Mar 1, 2023, 5:04 PM

#

yes, but how can I paste screenshot here?

terse wadi Mar 1, 2023, 5:06 PM

#

you should be able to do so (now 😄 ).

wind flame Mar 1, 2023, 5:06 PM

#

terse wadi Mar 1, 2023, 5:07 PM

#

is this log in the background made with our original code? Or did you already change the asset code here?

wind flame Mar 1, 2023, 5:08 PM

#

I just used/implemented your asset in our application. Source code is not modified

terse wadi Mar 1, 2023, 5:08 PM

#

perfect

#

So I got this situation, right?

You are changing the serverAddress field of the SocketIOCommunicator before calling Connect()
On Native build (or Editor) it is working
On WebGL it is not working - and according to the logs it tried to connect before "Connect()"

wind flame Mar 1, 2023, 5:11 PM

#

yes, exactly

terse wadi Mar 1, 2023, 5:11 PM

#

okay. Let me check this real quick

#

I can confirm this is a bug

wind flame Mar 1, 2023, 5:16 PM

#

you were able to reproduce this?

terse wadi Mar 1, 2023, 5:17 PM

#

better: I already found the issue in the code. I just have to elaborate how to fix it 😄

#

that part is a bit tricky

wind flame Mar 1, 2023, 5:17 PM

#

😀

terse wadi Mar 1, 2023, 5:19 PM

#

could you kindly open a ticket by mailing [email protected] ?
No need for long explainations, just copy my summary from above into the body and add your asset store invoice ID to verify the purchase.

I will then send a fixed version as soon as I got it done 🙂

wind flame Mar 1, 2023, 5:19 PM

#

yes, sure, thank you very much 🙂

terse wadi Mar 1, 2023, 6:35 PM

#

The lack of functionality in the v2 protocol does not make it too easy 😄

I am trying to backport the "new" Connect methods from our v3/v4 asset to keep it consistent

#Socket-io-v2 WebGL