Bug 242795 - In iOS 16 beta 20A5312j, Chrome 103 calls getUserMedia() will get black video
Summary: In iOS 16 beta 20A5312j, Chrome 103 calls getUserMedia() will get black video
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Other
: P2 Normal
Assignee: youenn fablet
URL:
Keywords: InRadar
: 243121 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-07-15 01:49 PDT by Yuwei Zhang
Modified: 2022-07-25 13:09 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuwei Zhang 2022-07-15 01:49:14 PDT
Summary:
In iOS 16 beta 20A5312j, Chrome 103 calls getUserMedia() will get black video.

Tested devices:
Bug is reproducible on:
-iPhone 12 | iOS 16 Beta 20A5312j

Bug is NOT reproducible on:

-iPhone 13 | iOS 15.5

Steps:
1. open https://webrtc.github.io/samples/src/content/getusermedia/gum/ with Chrome/firefox/other apps' webviews.
2. click Open Camera.

Actual result:
Black video

Expected result:
Video is available for WebRTC call from iOS User who has iOS 16 version installed on the mobile device.

Reproducibility:
100%
-----------------------------------------------------------------------------------


I noticed that the 20A5303i version fixes the getUserMedia black screen in safari.

Some of my users use chrome/firefox for WebRTC calls on iOS, or use other apps' webviews.

It seems like there are still some issues with WKWebview here that cause black video problems.
Comment 1 Radar WebKit Bug Importer 2022-07-15 17:38:57 PDT
<rdar://problem/97102894>
Comment 2 youenn fablet 2022-07-18 09:39:33 PDT
Pull request: https://github.com/WebKit/WebKit/pull/2512
Comment 3 EWS 2022-07-19 00:13:40 PDT
Committed 252591@main (19a6a3753222): <https://commits.webkit.org/252591@main>

Reviewed commits have been landed. Closing PR #2512 and removing active labels.
Comment 4 Alexey Proskuryakov 2022-07-25 13:09:03 PDT
*** Bug 243121 has been marked as a duplicate of this bug. ***