Unity iOS header frames can't be read issues
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
The websocket-sharp library seems to work fine when building for standalone and android targets but it fails when running on iOS (both on the iOS device and the UnityEditor). The following is the error message on the device:
FATAL|WebSocket.processException|WebSocketSharp.WebSocketException: The header part of a frame cannot be read from the data source.
at WebSocketSharp.WsFrame+<ParseAsync>c__AnonStorey14.<>m__21 (System.Byte[] header) [0x00000] in <filename unknown>:0
at WebSocketSharp.Ext+<ReadBytesAsync>c__AnonStorey5.<>m__D (IAsyncResult ar) [0x00000] in <filename unknown>:0
It seems to be failing at WsFrame.cs:650 where the header isn't being stored and parsed properly. I've spent some time trying to debug this but couldn't find the solution. Is there a workaround or a fix for this? Thanks!
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 at WsFrame.cs:650 and reproduce the header-read failure on an iOS device or in the UnityEditor, comparing it with standalone and Android behavior. Trace why the frame header is not stored or parsed correctly; done means the reported WebSocketException no longer occurs for the iOS Unity target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, ios, unity
- Domain
- mobile-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100