Frequently Asked Questions¶

Q: Whitch platforms are supported?¶

A: All major platforms are officially supported, specifically:

• Desktop: Windows, Linux, MacOS
• Mobile: iOS, Android
• Universal Windows Platform (UWP)
• Web: WebGL

• Furthermore, user reports suggest that Best Socket.IO also functions on the following platforms. However, due to the lack of testing capabilities, official support for these platforms is not provided:

  • Xbox
  • PlayStation
  • Nintendo Switch

  Please note that while there is evidence of compatibility with these platforms, I'm unable to offer official support or guarantee full functionality due to testing limitations.

Q: What is the supported Socket.IO version?¶

A: Best Socket.IO supports the latest version of Socket.IO: v4.x (Socket.IO protocol v5).

Below is a compatibility table for your reference, which includes compatibility with the Python based implementation, Flask-SocketIO too:

Q: What's the license of the plugin?¶

A: The Best Socket.IO plugin is licensed under the Unity Asset Store End User License Agreement (EULA). This means that your use, distribution, and modification of the plugin are governed by the terms and conditions set forth in the Asset Store EULA. For a detailed understanding of your rights and obligations under this license, please refer to the full Asset Store EULA text¹.

If you have specific licensing questions or concerns related to the Best Socket.IO plugin, please don't hesitate to reach out to our support.

Q: My Socket.IO servers are behind a load balancer (AWS ALB). How can I setup the asset to send the required cookies (AWSALB)?¶

A: The plugin handles necessary cookie management, so there's no need to set the cookies directly for every request. However, when built for the web (WebGL), cookies are managed by the underlying browser, and requests must be created by setting their withCredentials flag to true:

1
2
3
4
5
6

var options = new SocketOptions();
#if UNITY_WEBGL && !UNITY_EDITOR
options.HTTPRequestCustomizationCallback = (man, req) => req.WithCredentials = true;
#endif

var manager = new SocketManager(new Uri("https://myserver"), options);

Comments