-
Notifications
You must be signed in to change notification settings - Fork 217
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
Issues on iOS 17 in mobile Chrome and Safari #2023
Comments
I also am having another issue since the 17.4.1 of iOs : I think it's linked to the way apple resolve the problem, patch note here: https://support.apple.com/en-ca/HT214097 Available for: iPhone XS and later, iPad Pro 12.9-inch 2nd generation and later, iPad Pro 10.5-inch, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 6th generation and later, and iPad mini 5th generation and later Impact: Processing an image may lead to arbitrary code execution Description: An out-of-bounds write issue was addressed with improved input validation. When troubleshooting, I saw that the LocalVideoTrack isn't triggered as disabled or stopped so there is no way to detect when the video is cutted. |
On my iPad Pro (2020, 11-inch) running iPadOS 17.4.1, I am unable to join a call due to this issue. The video feed shows as black. Before updating to 17.4.1, this worked fine (but I don't remember the precise OS version that I was running before. I think it was 17.3 but not 100% sure) Are there any workarounds available? |
We are looking into this. Bear with us. |
echo'ing this, as soon as the second participant joins the call, the first participant video track gets black, they can still talk to each other, first participant needs to rejoin. I don't get any track subscription notices that I can work with. |
Hi folks, Apple have released a fix for this in iPadOS 17.5. |
We're facing a similar issue that shows on ios devices below iOS 17.5. |
We have detected a number of issues in mobile browsers while testing iOS 17 Beta. Please find the list of issues and their status in the table bellow. We are actively working on addressing all of them.
The text was updated successfully, but these errors were encountered: