You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've integrated a self hosted Jitsi aession into a room, via a self hosted dimension integration server. On element Web the Integration works flawlessly, on Element Android a never ending loading screen is all I get
To Reproduce
Steps to reproduce the behavior:
Setup a dimension Integration Server
Setup a Jitsi Server
Configure Element web to use this self hosted integration server.
Add a self hosted Jitsi session to a room via Element Web via the self hosted integration server.
Try to enter the Jitsi session in Element Android Voice/Video
Expected behavior
Element should open the jitsi session in the jitsi app installed on my android device
Screenshots
Smartphone (please complete the following information):
Device: One+ 8 pro
OS: Android 10
Additional context
App version and store: Play store 1.0.7
Homeserver: synapse:v1.17.0-py3
The text was updated successfully, but these errors were encountered:
I have my own account and two test dummies. Both Test dummies are connected via Element Web (also self-hosted). My own account is connecting via Android (Samsung Galaxy, Android 11, Element 1.0.17 from F-Droid). All 3 accounts are joined into a testing room. No matter from where i initiate a call, all participants can join the call using my self-hosted Jitsi server. No issues on Android here. It also works using Schildichat (version 1.0.14.SC27 F-Droid).
Describe the bug
I've integrated a self hosted Jitsi aession into a room, via a self hosted dimension integration server. On element Web the Integration works flawlessly, on Element Android a never ending loading screen is all I get
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Element should open the jitsi session in the jitsi app installed on my android device
Screenshots
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: