Corrupted data on WebSocket channel

Hello,

As a developer, I'm experiencing a problem with WebSocket connections since upgrading to MacOS 15.0 Sequoia.

When using a JSON RPC API from my workstation using tools such as Postman and/or Docker, I encounter the following problem: At the start of communications, messages received on the WS channel are fine. But after a while (indefinite) the messages become corrupted, truncated or jumbled.

For debugging purposes, I used the WireShark utility to confirm that the problem was not with the server itself. I was thus able to confirm that incoming WebSockets messages are not corrupted, whereas they are when received by Postman and/or Docker.

To confirm my hypothesis that the problem appeared with the latest version of MacOS, we tested on 6 different workstations.

  • 3 MacBook Pro 13” running MacOS 14.6
  • 3 MacBook Pro 13” running MacOS 15.0

The results were clear: the 3 MacOS 14.6 workstations never encountered the problem of corrupted data on the WebSocket channel, whereas the 3 MacOS 15.0 workstations did.

Should you require any further information, please do not hesitate to contact me.

Yours faithfully

Paul BESRET, R&D Engineer.

What API are you using for your WebSockets implementation on macOS? Network framework? URLSession? Or is this within Safari?

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thank you for your prompt response.

In our case, we are not directly implementing WebSockets using a specific macOS API. The issue is observed in third-party applications that use WebSockets: Postman and/or Docker.

In both cases, we're not directly using macOS APIs like Network Framework or URLSession. Instead, we're observing the issue in these applications running on macOS 15.0.

The problem appears to be at the system level, as it affects multiple independent applications. Our Wireshark analysis shows that the data is intact when it reaches the system, but becomes corrupted when it's delivered to these applications.

Given this information, we suspect there might be an issue with how macOS 15.0 is handling WebSocket connections at a lower level, which is then affecting applications that rely on the system's networking stack.

Is there any additional information you need or any specific tests we can run to help diagnose this issue further?

The issue is observed in third-party applications that use WebSockets: Postman and/or Docker.

So, just to be clear, you’re seeing this with the Postman Mac app downloadable from here:

https://www.postman.com/downloads/

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Absolutely. That's one of the third party applications in which I have been able to reproduce the bug.

Corrupted data on WebSocket channel
 
 
Q