-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
IFrame API Not working in IOS Browser #6885
Comments
What Jitsi package versions are you running? |
You shouldn't need to do this because you already use: |
we are using the version is 10. Can you please let me know what code updations i can do to make it work in ios browser? |
10 is not a version we have released. How did you install jitsi in your server? If it was using the Debian packages, then do |
I will give you an update soon. is the issue beacause of that running version? |
Maybe, but we need to know which version you have in order to know what fixes you might be missing. |
this issue only happens when the chatroom works in Iframe API. if we directly access the url it works in iphone browser. |
Sorry for the verson info 10 .it was a mistake |
A number of Safari related fixes have been added since. Can you please update to the latest stable (released yesterday) and re-test? |
can you please let me know the release version details. So we can update and check. |
What details do you need? It was pushed to out repo, so |
Thank You we will update. eg: |
You need to use JWT authentication in that case. |
is it possible to do in the server settings when creating the chatroom? |
It's not a server configuration thing (other than enabling token authentication). Each token has a room attribute and then the user would only be allowed to that room. But you need to generate the tokens yourself. |
Hey @saghul We were testing your latest JITSI updates and we still can't make iOS work using iFrame API on Safari. We tried this on iOS 13 on iPhone and iPad. Video still not working. Even for the audio, we have to manually unmute the microphone. Please find our jitsi packages information -> please let us know if you need anything else to troubleshoot this issue. Thank you |
@jallamsetty1 ^ are these the issues you were looking into? |
Video should be working fine, audio is the known issue and the workaround for that is to tap on the camera icon in the safari tab twice to disable and enable it as described above. |
We're using the iframe API and this is not working for me either regardless of how many times I activate and deactivate the camera when using Safari on iOS. Using Chrome on iOS it just crashes. |
The audio issue should be fixed, we pushed a change to the master. It should be available in the unstable repo or you can try IFrame API against https://alpha.jitsi.net. |
@saghul |
Can you please message? Its not working in iPad. Just showing a blank page. |
@jallamsetty1 why IFrame API not working in ipad. its working in android chrome and iphone. when we check in ipad its not working. its showing a blank page. do you have any fix for this? |
Have you tested what @jallamsetty1 suggested? Can you gather browser console output? (You can do that with the remote inspector). |
Hi, @saghul Audio and Video works. But are you guys working on Microphone bug? Why we have to double-tap on microphone to unmute it in an iframe. |
I’m not aware of such issue. |
Gotcha. Let me explain the issue. We are using JITSI API and are creating a conference session. But when we use this on safari iOS, by default our microphone is muted and we have to double click on microphone to unmute ourselves along with the video camera. |
@SharadKumar97, have you tried the nightly build ? double-tapping on the camera icon in the address bar was a workaround for the audio bug that has been fixed in the nightly build. Are you referring to a different issue ? If so, please provide the logs to help us debug it further. |
Now we tested in ipad. Now its working both audio and video in safari. Thank you @jallamsetty1 and @saghul |
Hi. We tested the nightly build and it's fixed there. Thank you |
@jallamsetty1 when one customer tried in ios(iphone). he don't access the camera. can you please let me know is there any version issues affecting. |
This issue doesn't seem to be specific to iOS only. Mobile browsers in general seem to be more restrictive, previews of all available cameras is not working on the android phone I tested using chrome and Firefox. Can you please check if it works well from the device settings menu instead of the camera button pop-up ? |
@jallamsetty1 can you please let us know what browser settings we have to check. because some clients says that it is not working they are not able to access camera.This issues also happens when shifting the front camera and back camera. When shifting camera front camera screen shows black. |
Yes, looks like the browser on mobile doesn't seem to return a second stream from the same camera, this is what we try to do when we try to get a preview for the camera selection popup from the video button. Though you see a black screen for the preview, you should be able to switch to the rear camera there. We will be working on optimizing all these settings for the mobile browsers but in the meanwhile you can try to use the device selection menu from the following |
I have the same problem, the fullscreen option in iframe api is not working on ios with safari browser. |
Description:
Hi we have implemented jitsi in our server. we use IFrame API for websites.its working fine in desktop. but when we access the page through mobile browser it works fine in chrome from android device. But it is not working in IOS device (safari browser).We need this to be work in ios also
Steps to reproduce:
Expected behavior:
When page open in IOS browser the video and audio should work.
Actual behavior:
Now when taking in ios browser video not working.
Additional information:
We made it working in the mobile browser by following update in app.bundle.min.js
change in /usr/share/jitsi-meet/libs/app.bundle.min.js
Here is the IFrame API
The text was updated successfully, but these errors were encountered: