Open ara4n opened 6 years ago
I'd be ready to work on this if anyone could share information i'd be happy to share
Note that the issue happens also when the app is in the background, or hasn't been started yet - it's not directly related to locked screen.
I'm trying to investigate a little...
comparing the logs of when it works and when it doesn't, and grepping for "MXJingleCallStackCall", I shows this potentially interesting difference:
(...)
Riot[3642:355100] [MXJingleCallStackCall] didGenerateIceCandidate: RTCIceCandidate:
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceGatheringState: 2
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 2
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 5
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 6
Riot[3642:355100] [MXJingleCallStackCall] didChangeSignalingState: 5
(...)
Riot[3642:355100] [MXJingleCallStackCall] didGenerateIceCandidate: RTCIceCandidate:
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 6
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceGatheringState: 2
Riot[3642:355100] [MXJingleCallStackCall] didChangeSignalingState: 5
which causes then the MXCallState
to go from MXCallStateConnecting
to MXCallStateEnded
(when failing, the log shows [MXCall] setState. old: 6. New: 8
) instead of MXCallStateConnected
(when working OK, the log show [MXCall] setState. old: 6. New: 7
)
Will look at it more but if anyone has an idea...
Per discussion with @manuroe , most likely the first step toward a fix would be to upgrade the webRTC libraries that are very old. See https://github.com/vector-im/riot-ios/issues/1483#issuecomment-469594287 and subsequent comments
Per discussion with @manuroe , most likely the first step toward a fix would be to upgrade the webRTC libraries that are very old. See #1483 (comment) and subsequent comments
^ Sadly, upgrading to the latest version (v0.8.6) doesn't seem to solve the issue. This is really annoying and a show-stopper in every way.
if you hit the video button to try to turn on the camera, it sits there stuck in 'connecting' state after you unlock the screen