{"type":"WebSocketError","error":{"isTrusted":true}}

[sobrinho]

Do you want to request a feature or report a bug?
BUG

What is the current behavior?

{"type":"WebSocketError","error":{"isTrusted":true}}

If the current behavior is a bug, please provide the steps to reproduce and
if possible a minimal demo of the problem via https://jsfiddle.net or similar.

Not sure how to reproduce, here's the backtrace:

What is the expected behavior?

No errors with events (looks like an event due to the isTrusted).

Which versions of Pusher, and which browsers / OS are affected by this issue?
Did this work in previous versions of Pusher? If so, which?

Pusher: 8.0.2

[benjamin-tang-pusher]

Could you try testing your phone in our test site test.pusher.com? Is your iPhone's Safari browser able to connect there?

[sobrinho]

Works fine on my phone but we are seeing this repeatedly in production for a bunch of different users with unstable connections.

[Janiczek]

Some of our users are hitting this too.

[benw-pusher]

This appears related to some fallback protocols that are used when the websocket connection can't be maintained.
Do you have any insight into the behaviour of the client at the time these errors are encountered? I would be interested to know if the device is able to establish a connection once the network conditions stabilise - it could be that these errors are encountered during the instability, which would be expected to some extent as the connection is severed.