[Plugin] Socket.io Client

[getnamo]

@Skalbe

Heya! Truly appreciate your activity here.
Funnily enough my server test project stopped connecting to my local server from Quest after a rebuild again and I haven’t a clue why, as I did not change any content. The rebuild was a sanity check test after I had replicated the settings to the main project with the content etc and it wouldn’t work there either.
I have tried cleaning everything through the ADB, uninstalling from Quest, rebuilding with deleting Intermediate folders etc, but nothing helps. I suspect it’s something with the settings of permissions when deploying to the Quest, but I really don’ t know. Would you perhaps have some pointers, as you are also working with the Quest?
I definitely had it working once and I could just launch the server and launch the app from the quest and it connected, but no more.
The next step that I will try is building with socket.io, I suppose, but I am building from Oculus 4.25.3 sdk branch and it keeps saying that the plugin is made for 4.25.0 and disabling it on build.

Edit: still struggling to achieve consistent behavior for the connectivity. Sometimes when I build to Quest, it connects to the dedicated server, sometimes it just doesn’t.
And when I build server with socket.io, it gives me this: Screenshot by Lightshot
Am I supposed to install some third party stuff for this to work?

if its disabling the plugin it won’t work right. If you’re using a custom branch remove the engine version field from uplugin file and make sure your project has socket.io client plugin as a dependency in the uproject file.

With those, recompile your project and it should re compile the plugin for your engine version.

Usually when I dev quest stuff I just use a canonical engine version and select android as build target with relevant oculus plugins enabled, so YMMV.