Rick LUPPINO comentou,
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...
Rick LUPPINO criou uma publicação,
When my iOS app receives an incoming call and that call is answered, the audio stays only on the device speaker and not on the loud (hands free) speaker. That is, I need to hold the device up to my...
Rick LUPPINO criou uma publicação,
When my app is inactive or has been killed and an incoming call is received, the native CallKit UI is displayed as expected. When I answer the call, the app is opened by the iOS operating system bu...
Rick LUPPINO comentou,
I just noticed this error message in the console: [EncryptionManager:94] decryptDataString: failed to decrypt received data!
Rick LUPPINO comentou,
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 ...
Rick LUPPINO comentou,
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.
Rick LUPPINO comentou,
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...
Rick LUPPINO comentou,
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...
Rick LUPPINO comentou,
It appears that remoteVideoTrack is indeed the same in both cases. VideoStream approach: VideoTrack approach:
Rick LUPPINO comentou,
This is the code that works: if let remoteVideoStreams = ServicesManager.sharedInstance()?.rtcService.remoteVideoStream(for: self.currentCall!) { if remoteVideoStreams.videoTracks.count > 0 { ...