Steps:
- Join zoom meeting with joinMeeting
- Press “<” to minimise the ongoing call
- See that the call minimises, we see its PiP view and see our app screen too
- Maximise the zoom call
- Again minimise it,
- Now see that we see the PiP zoom call BUT we do not see our app screen (as it is getting destroyed)
Our app is a hybrid android cordova app, we have applied the setting to save the webview instance from getting destroyed.
disableClearWebKitCache(true);
With this setting, the MainActivity(which hosts the WebView) is saved from getting destroyed for the first time. But when we maximise the meeting again and then again press back, the app (MainActivity instance) gets destroyed.
We have done the following settings to the zoom call before joining the meeting :
zoomUIService.enableMinimizeMeeting(true);
zoomUIService.disablePIPMode(false);
zoomUIService.setNewMeetingUI (NewZoomMeetingActivity.class)
Where NewZoomMeetingActivity extends NewMeetingActivity
Activity stack :
-
When zoom call in progress
- NewZoomMeetingActivity
- MainActivity
-
When we press “<” call to minimise → our app is shown and call is shown in PiP
- com.zipow.videobox.conference.ui.ZmConfPipActivity
- MainActivity
- NewZoomMeetingActivity
-
Maximise the zoom call
- NewZoomMeetingActivity
- MainActivity
-
Again press “<” to minimise the zoom call
- com.zipow.videobox.conference.ui.ZmConfPipActivity
- NewZoomMeetingActivity
Our app instance is destroyed and if we maximise and then leave meeting we dont see our app until we relaunch it.
Please suggest a way by which zoom wont end the app/activity instance when switching to PiP mode.