Oculus go closes socket with 1006 after message
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
So everything was working fine on PC, then I tried to run same app on Oculus go and had some problems. The message is send and received by Oculus go websocket server but then suddenly stops with 1006 error code. What could be the reason? Here is my code.
https://github.com/jaroslaw-weber/gobof_unity/blob/master/Source/GobofCore.cs
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Source/GobofCore.cs code and the websocket-sharp handling of abnormal closure code 1006. Compare the Oculus Go behavior with the working PC case and gather a reproducible trace showing when the connection closes. Done means the platform-specific cause is identified and covered by a verified fix or a documented reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100