Bug 230698 - REGRESSION: getUserMedia camera stream fails after viewing a screenshot
Summary: REGRESSION: getUserMedia camera stream fails after viewing a screenshot
Status: RESOLVED DUPLICATE of bug 230538
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: Other
Hardware: iPhone / iPad Other
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-09-23 11:00 PDT by Joel Udwin
Modified: 2021-09-29 02:28 PDT (History)
3 users (show)

See Also:


Attachments
Camera Feed Turning Black on iOS 15 (18.89 MB, video/mp4)
2021-09-23 11:00 PDT, Joel Udwin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joel Udwin 2021-09-23 11:00:34 PDT
Created attachment 439068 [details]
Camera Feed Turning Black on iOS 15

On iOS 15 getUserMedia camera stream fails after viewing a screenshot (instant markup). This previously worked on iOS 14.8.

After the users exits the instant markup view, Safari give no indication of a change (‘VisibilityChange’, ‘pageshow’ are not called). At this point, (video.videoWidth>0 while video.currentTime remains 0).

Reproduction Steps:
1. Open https://webrtc.github.io/samples/src/content/getusermedia/gum/ on iOS15
2. Take a screenshot by pressing the power button and the volume up button
3. Open the screenshot preview (instant markup)
4. Either press delete, or save
5. The camera feed is now black (getUserMedia camera stream has failed)

Attached is an example video on iOS 15

Please let me know if I can provide more info, thank you.
Comment 1 Radar WebKit Bug Importer 2021-09-29 02:24:34 PDT
<rdar://problem/83662830>
Comment 2 youenn fablet 2021-09-29 02:28:31 PDT
Thanks Joel, I think this is indeed a regression where camera track gets muted.
This is detectable using onmuted.
But we do not unmute when getting back.
Putting Safari in the background for a second then back to foreground is unmuting the track.
This is most probably https://bugs.webkit.org/show_bug.cgi?id=230538.

*** This bug has been marked as a duplicate of bug 230538 ***