MASTER and VIEWER disconnected from the signaling channel after 5 mins using Safari iOS v15.5^
trianlandicho opened this issue · 5 comments
We've tried to test on KVS Testing Page using Safari iOS v15.5 and above on mobile devices. The signaling channel closed at the 5-minute mark and received these errors:
[2022-09-12T08:14:27.976Z] [ERROR] [VIEWER] Signaling client error: { "isTrusted": true }
[2022-09-12T08:06:32.064Z] [ERROR] [MASTER] Signaling client error
The video also cuts off intermittently and turns the screen to black
Is anyone experiencing the same issue?
Hi @trianlandich, what are you using as master? Can you share complete master and viewer-side logs?
Hello @niyatim23, I've used iPhones with iOS v15.6 for both Master and Viewer. Here is the log from the Viewer, the record from the Master is almost the same as the Viewer but the only difference is the error that is thrown: [2022-09-12T08:06:32.064Z] [ERROR] [MASTER] Signaling client error
LOG
[2022-09-12T08:09:37.523Z] [INFO] Page loaded
[2022-09-12T08:09:53.131Z] [INFO] [VIEWER] Starting viewer connection
[2022-09-12T08:09:54.423Z] [INFO] [VIEWER] Connected to signaling service
[2022-09-12T08:09:55.870Z] [INFO] [VIEWER] Creating SDP offer
[2022-09-12T08:09:56.639Z] [INFO] [VIEWER] Sending SDP offer
[2022-09-12T08:09:56.645Z] [INFO] [VIEWER] Generating ICE candidates
[2022-09-12T08:09:56.695Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.698Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:56.701Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.704Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:56.708Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.711Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:56.713Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.715Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:56.744Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.746Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:56.748Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.751Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:56.753Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.755Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:56.758Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:56.761Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:57.308Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:57.311Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:57.321Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:57.323Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:57.326Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:57.328Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:57.379Z] [INFO] [VIEWER] Generated ICE candidate
[2022-09-12T08:09:57.381Z] [INFO] [VIEWER] Sending ICE candidate
[2022-09-12T08:09:57.420Z] [INFO] [VIEWER] Received SDP answer
[2022-09-12T08:09:57.439Z] [INFO] [VIEWER] Received ICE candidate
[2022-09-12T08:09:57.451Z] [INFO] [VIEWER] Received remote track
[2022-09-12T08:09:57.454Z] [INFO] [VIEWER] Received remote track
[2022-09-12T08:09:57.505Z] [INFO] [VIEWER] All ICE candidates have been generated
[2022-09-12T08:14:27.976Z] [ERROR] [VIEWER] Signaling client error: {
"isTrusted": true
}
[2022-09-12T08:14:27.980Z] [INFO] [VIEWER] Disconnected from signaling channel
Hi @trianlandicho, did you solve this issue? Or do you have any idea how to solve that? I'm facing the same issue on macOS Chrome.
What error shows up in the browser console? The full error object should be printed there.
We are unable to replicate. Note that the kvs signaling channel has a hard idle timeout of 10 minutes. However, master/viewer should be able to still communicate to each other past that.
Using Chrome 113.0.5672.126 (master) along with Safari 16.4 (viewer) on MacOS for 20 minutes, I am still able to send/receive video between the two peers past the 5 and 10 minute marks.
Closing due to no response. Please update your Safari version and try out the latest webpage and see if the issue persists. If you could also share the full error that gets printed to the browser's debug console that would be great.