Android/ Call in process remain after leaving the meeting
See original GitHub issueDescription
On Android R after leaving a Jitsi meeting the app remains the call open. Which it’s causing problems in others apps or even opening a new meeting.
Is asking the following:
Current behavior
Calling view.dispose() it’s leaving the call open.
Expected Behavior
After on JitsiMeetActivity and calling view.dispose() the call should be also be terminated.
Possible Solution
Steps to reproduce
I’m using JitsiMeetView and JitsiMeetViewListener
This how I build the meeting conference :
JitsiMeetConferenceOptions options = new JitsiMeetConferenceOptions.Builder() .setServerURL(serverURL) .setSubject(" ") .setRoom(roomName) .setAudioMuted(startWithAudioMuted) .setVideoMuted(startWithVideoMuted) .setWelcomePageEnabled(false) .build(); view.join(options); setContentView(view);
This is trigger after I left the meeting :
@Override public void onConferenceTerminated(Map<String, Object> data) { view.dispose(); view = null; finish(); on("onConferenceLeft", data) }
- Try to join into a JITSI meeting
- Left the meeting and you will see the call icon at the top menu.
- This is only happening on Android R.
** Just in case I’m using Ionic React and capacitor
Environment details
implementation (‘org.jitsi.react:jitsi-meet-sdk:2.+’) { transitive = true } Android Version : R
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (1 by maintainers)
Top GitHub Comments
@nedimf updated. let me know if it clear enough.
@saghul I set flag like this but is still happening :
JitsiMeetConferenceOptions options = new JitsiMeetConferenceOptions.Builder() .setServerURL(serverURL) .setRoom(roomName) .setFeatureFlag("call-integration.enabled", false) .setToken(token) .setSubject(" ") .setAudioMuted(startWithAudioMuted) .setVideoMuted(startWithVideoMuted) //.setAudioOnly(false) .setWelcomePageEnabled(false) .build(); view.join(options); setContentView(view);
I am missing something ?