Closed 1045672215 closed 8 months ago
@1045672215 ,
Can you confirm if you invoke signalingClientConnectSync
after signalingClientFetchSync
? The signaling connection duration has a hard 1 hour limit. Wondering if you are hitting the limit during wake up.
We use the webRTC on battery devices with sleep and wake up functions and want to achieve that devices are able to watch living streaming immediately after waking up.
Any design considerations/constraints Before v1.7.0, we call freeSignalingClient function before sleep and call createSignalingClientSync function after wake up.It works.But when we update the sdk after v1.7.0, we only call signalingClientFetchSync function before sleep, we find devices can't receive SDP Offer after wake up. (Devices has been connected to the signaling server and can receive ICE candidates.)We try to call signalingClientFetchSync function after wake up,but it didn't solve the problem. So we want to know how to use signalingClientFetchSync on battery devices to solve the problem.