Android SDK. There's already another call in progress. Please end it first and try again.
See original GitHub issueHello,
Android SDK 19.4.0. I have found that when my application launches the Activity that extends JitsiMeetActivity JitsiMeet works well with both the Jitsi server endpoint (https://meet.jit.si) and my own server endpoint. This setup uses the default Jitsi UI like the welcomepage.
However, if i launch this activity from another custom activity (my own welcome page), the first join attempt is successful but every subsequent join attempt after the first successful join fails with a dialog displaying that says:
“There’s already another call in progress. Please end it first and try again.”
This doesn’t make sense as to return to the previous activity that the join button exists on, I must first have had to End the call.
What is so different between the Apps default activity launcher being the activity that extends from JitsiMeetActivity as opposed to launching that activity through an intent?
Update:
The call connection is being retained after hanging up the call. I exposed the method abortConnections()
in ConnectionService
and trigger it and wait for the logs from ConnectionImpl
, onDisconnect()
to confirmed state disconnected.
After doing this, the next subsequent attempt to join a conference is successful.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (4 by maintainers)
Top GitHub Comments
There you go 😃
The default options apply to all conferences, adn are re-applied after one ends. Because you are setting a room there, it will re-join it. I’ll try to come up with something to make this more obvious, or throw an exception.
You must create a new object which you pass to
join
, and call setRoom on that one.Same goes for
setUserInfo
. Just set the server on the default ones.Can you explain more as to how to call leave() is it a predefined function? if not what all to add?