Uncaught (in promise) Timeout to make rpc to [email protected]_39.onSessionSignaling

[hexray-newbee]

chrome console

owt.js:3300 MCU returns negative ack for unsubscribing, Invalid subscription id
owt.js:3374 Empty candidate.
owt.js:4754 Uncaught (in promise) Timeout to make rpc to [email protected]_39.onSessionSignaling
handleResponse @ owt.js:4754
(anonymous) @ owt.js:4922
r.onack @ index.js:83
r.onpacket @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
r.ondecoded @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
a.add @ index.js:83
r.ondata @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
r.onPacket @ index.js:83
(anonymous) @ index.js:83
r.emit @ index.js:83
r.onPacket @ index.js:83
r.onData @ index.js:83
ws.onmessage @ index.js:83

https://github.com/open-webrtc-toolkit/owt-client-javascript/blob/d727af2927731ff16214d73f57964a992258636d/src/sdk/conference/channel.js#L442

https://github.com/open-webrtc-toolkit/owt-client-javascript/blob/f8403a42f4a98070a52cbf40fb715d64646dd68b/src/sdk/conference/client.js#L296

owt.js:4922 https://github.com/open-webrtc-toolkit/owt-client-javascript/blob/f8403a42f4a98070a52cbf40fb715d64646dd68b/src/sdk/conference/signaling.js#L153

owt.js:4754 https://github.com/open-webrtc-toolkit/owt-client-javascript/blob/f8403a42f4a98070a52cbf40fb715d64646dd68b/src/sdk/conference/signaling.js#L20

[jianjunz]

It looks like there is an error at server side. I think you could reopen the issue you reported at owt-server.

[hexray-newbee]

and why uncaught reject?

[jianjunz]

If it is caught in SDK, how could application know that the operation is failed?

[hexray-newbee]

Which function may throw this rejection? leave?

[jianjunz]

If you see this error without calling any method, it might be something wrong at server side. And this message should be handled in SDK. SDK may fire an event to let application know.

[hexray-newbee]

Does the rejection fire "messagereceived"?

[sebsken]

FYI, there is a similar issue on the server repo https://github.com/open-webrtc-toolkit/owt-server/issues/989 and it happens without using any client. So this is definitely related to the server and not the client.