Closed suhailzoft closed 3 years ago
ghost
commented
3 years ago @suhailzoft Hello,
This is Nikolay from QuickBlox support.
According to my check, you already submitted a ticket and the issue is being investigated.
Once there is any news, we will let you know.
QB-maksym-pidhorbunskyi
commented
3 years ago @suhailzoft Hello,
This is Maksym from the QuickBlox support.
According to the provided details in the ticket that you submitted via Help Center and code review by our Flutter developer on a paid basis, the root reason of the issue has been found.
In general, the issue relates to wrong logic for calling Flutter SDK methods. The video views (remote and local) have controllers which render (play) the video tracks. In your implementation the play method was called earlier than controllers are ready. It’s producing the issue which that you described.
Wrong workflow:
Correct workflow:
Additionally, once the call ends, you need to call QB.webrtc.release(); in order to release a resource. release() method should be called when a video track is no more valid. If you don't call this method, you will get a memory leak.
The detailed workflow of video calling can be found in our official documentation
We consider this issue as resolved and move it to Closed.
When i try to trigger a call to iOS device, local video become black screen. But, remote video working fine.Also, local video and remote video from the iOS device showing well in the web where we initiated the call.It's not happening every time.Also,It's working well in android devices.Please help me to solve this issue ASAP.