-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jitsi choose room page shown instead of finishing the call #25390
Comments
That Element instance uses a custom Jitsi instance |
I am the "aarenet admins" contacting you to ask if you know anything about why this is happening... 😅 What configurations do you think are wrong? is it on the Jitsi side or the Element side? |
Element just iframes Jitsi using the JitsiMeetAPI, the behaviour is all defined by Jitsi's config |
I thought there is more to the integration between Jitsi and Element... This page is part of it is it not? Usually after a call is over it goes back to this page, which is not related to the Jitsi Meet project... I'll try reproducing the issue on matrix.org and jitsi.riot.im but I think this issue is still relevant, could you re-open it please? |
That page is the one which uses the JitsiMeetAPI when you press the It'll go back to that page when the Jitsi Meet API says that the call is over by signalling I can re-open it but I honestly doubt there is anything Element can do when Jitsi doesn't tell it |
ok, thanks a lot ! |
looks like this is actually a bug - someone internally encountered it. When it happens, please submit logs. |
just sent logs @turt2live |
Stale. Bah, @t3chguy you tricked me! |
Description
Jitsi choose room page shown instead of finishing the call.
Steps to reproduce
not sure but this happens sometimes when leaving a jitsi conference call
the join button should appear...
This is particularly disturbing because picture in picture is still active and the conference needs to be ended for everyone..
Logs being sent: no
Version information
For the web app:
The text was updated successfully, but these errors were encountered: