Closed alvarhansen closed 7 years ago
Hi @allu22,
We do occasionally make blocking calls into WebRTC classes from the developer's calling thread and the notifier queue that was provided when constructing TVIVideoClient
(the main queue by default). However, the duration of the calls into WebRTC should be very short. It sounds like in your app the blocking call either lasts forever or for a long time?
I should mention that our 1.0.0-beta6
release has some improvements to WebRTC resource management that may resolve the issue you are experiencing.
Cheers, Chris
Hi @allu22,
Upon further inspection it looks like you are hitting a backgrounding case which is not currently supported by our SDK.
1. User1 joins room (in app)
2. User1 sends app to background
At this point the audio subsystem is not active, and since you (presumably) aren't using CallKit iOS puts the app into a deep sleep. Our SDK misbehaves and does not recover from the deep sleep properly in this scenario. This is a known issue that we are working to resolve in future beta releases. I'll update this ticket once we have a fix.
https://www.twilio.com/docs/api/video/changelogs/ios
Best, Chris
Hi @allu22,
Our 1.0.0-beta9 release has some fixes for crashes and misbehavior while backgrounding. Please give it a try when you get the chance. If you have any problems feel free to drop us a line at: https://github.com/twilio/video-quickstart-swift/issues/89
Cheers, Chris
We are getting main thread blocked in our app when following scenario happens:
func room(_ room: TVIRoom, participantDidDisconnect participant: TVIParticipant)
in response we do that. )Stack trace from lldb using
bt all
"Crash" log: