Hi Christophe, Thanks for the sample code. I had modified our code to handle the asynchronous calls better and got it working reliably but your example has helped me to improve that even further. ...
Further to the above, I can see in my device console logs that in the event that the app is killed, a call is received and the answer button on the CallKit UI is pressed, the call is actually not b...
I just noticed this error message in the console: [EncryptionManager:94] decryptDataString: failed to decrypt received data!
I am having the same issue where the "decryptNotificationContent" function of the notificationManager is not decrypting the payload and is returning the exact same content as before decryption. Is ...
OK. I have tried that but it didn't solve the problem. I can continue to use the video stream approach for the time being.
The log is 100's of lines and will be too large to paste here. Is there a way to send it to you directly? via the Rainbow app maybe? Or is there a specific section you're looking for? NSLog here: 2...
Sorry, I misunderstood. Here is the result when doing both approaches in the same test. remoteVideoTrack is from the remoteVideoStreamFor approach and remoteVideoTrack2 is from the remoteVideoTrack...
It appears that remoteVideoTrack is indeed the same in both cases. VideoStream approach: VideoTrack approach:
This is the code that works: if let remoteVideoStreams = ServicesManager.sharedInstance()?.rtcService.remoteVideoStream(for: self.currentCall!) { if remoteVideoStreams.videoTracks.count > 0 { ...
This is still happening in the latest LTS version of the SDK (2.4.0). I'm adding the remote video track to the view (RTCMTLVideoView) in the didAddRemoteVideoTrack event but the stream does not ren...