You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@avivash and @bgins have confirmed that when NSURLSession Websocket is disabled, the error goes away. This feature can be turned off by unchecking NSURLSession Websocket in Develop -> Experimental Features.
I've encountered this issue too with a WebSocket server using HTTP/2 + TLS 1.3. The connection succeeds at first and I'm able to send and receive some (short) WebSocket messages, but then the connection gets disconnected with the aforementioned "kNWErrorDomainPOSIX error 100 - Protocol error" error message. A longer message sent by the server seems to cause the disconnection.
The root issue is likely a Safari bug, but we may be able to work around it.
Summary
Problem
Safari fails to establish a WebSocket connection with peers.
Impact
Data cannot be published or synced without a connected WebSocket.
Solution
Needs investigation.
Detail
Describe the bug
When authenticated and using a web app in macOS Safari, the console reports errors like:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error should be reported and file system operations that rely on peers should work.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: