We are having an interface where the user will be able to see the list of meetings for the day irrespective of meeting type for eg., Zoom Meeting , ABC or XYZ and so on.
We are trying to use a third party library where it has an android webview loading the meeting interface. The meeting interface is being loaded properly on the webview but the WebRTC connection is not established since it is blocking to show the camera video once the user grant the camera permission.
This behaviour is happening due to the the Zoom SDK initialisation happened once the screen loads where list of meetings are being shown. As per the observation the Zoom SDK contains mobilertc module which may be trying to block other WebRTC connection. We also tried not to initialise the Zoom SDK, there after the behaviour was same.
The reason for specifying the above observation because if the above integration is done in a separate android branch where it doesn’t contains the Zoom SDK , things are working fine as we expected the camera video is also being shown due to successful WebRTC connection.
Is there a way to handle the Zoom mobilertc module not to get initiated even if the Zoom SDK is not being initialised by us manually ? Or How can we proceed further with this ?
Please find the screen records for the issue when the zoom sdk is initiated and another video which doesn’t contain zoom SDK at all.