I am developing an AR app that can track a user's hand locations and export that data via WebSocket to my (or someone else's) computer. I have a Unity Script which acts as a WebSocket Client that sends data to a basic WebSocket Server that is on my computer. This connection and, more importantly, the code worked for me a couple of months ago. This is important because I am using the same WebSocket code and changed very little else to do with the project since then. One of the big things that I have changed is switching from Quest 2 to Quest 3, so the problem is likely with Quest 3.
Through troubleshooting, I have ruled out the following things as issues:
- The wifi network blocking connections to the headset due to firewalls/restrictions
- Issues with the WS Server on my computer not being able to receive data
- Issues with the current version of WebSocket Sharp that I am using
- Issues with the current version of Unity that I am using
- Referencing the wrong IP address in the WebSocket Client
- Something wrong with my computer that isn't reproduceable on other computers
I am going to try running my app on my Quest 2 tonight instead of Quest 3, and if it works then I know the issue is with Quest 3. If this is the case, what can I do to fix this? Has anyone gotten WebSockets working on Quest 3? I have heard that network permissions can cause this issue, but nothing I have found in either the Quest's or Unity's settings have made a difference. Please help me out
I eventually discovered that WebSockets encounter an issue with the Quest 3's Network and Security Permissions, and I tried to trouble shoot it for weeks to no avail. Instead, I used MQTT as an alternative. Because of its publish-subscribe model as opposed to a handshake/direct connection format, it doesn't run into issues with the permissions of the headset. There is a tradeoff, as the data streaming isn't quite as fast, but it worked great for my purposes. Additionally, there is a GitHub repo that makes it fairly easy to just add a script to your project and get it working very quickly. To any Meta employees reading this, please address this WebSocket issue, it is a great hinderance to IoT projects.
