Bug 231365 - REGRESSION (iOS 15.1 beta): Returning to a black screen with peer connection after backgrounding Safari
Summary: REGRESSION (iOS 15.1 beta): Returning to a black screen with peer connection ...
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: Safari 15
Hardware: iPhone / iPad Unspecified
: P2 Blocker
Assignee: Nobody
Keywords: InRadar
Depends on:
Reported: 2021-10-07 09:37 PDT by Virginia Farley
Modified: 2022-02-12 19:34 PST (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Virginia Farley 2021-10-07 09:37:27 PDT
After setting up a RTCPeerConnection in Safari 15, if you switch to another application and then return back to the website, the video screens are black.  This behavior can be seen on the https://webrtc.github.io/samples/src/content/peerconnection/pc1/ sample page.

The steps to reproduce this bug are:
1. Open https://webrtc.github.io/samples/src/content/peerconnection/pc1/ 
2. Click the "Start" button, allow microphone and camera access when prompted, then press the "Call" button
3. Switch to another application for 3-5 seconds
4. Return to the Safari and observe that both video screens are black 

Expected behavior: After backgrounding Safari and coming back, video resumes. 

Able to reproduce with iOS 15.1 beta. Unable to reproduce with iOS 15.0.
Comment 1 Radar WebKit Bug Importer 2021-10-11 10:09:18 PDT
Comment 2 Kongpheng 2021-10-25 18:37:07 PDT
I was able to reproduce this issue too on iOS 15.1 (19B74).

Alternate reproduction steps:
* Open https://webrtc.github.io/samples/src/content/peerconnection/pc1/
* Click Start button
* Grant access to microphone and camera
* Notice video is captured
* Make a call to the iPhone
* From Call UI dialog, decline it
* Notice that video doesn't get auto-resumed, instead you see a black rectangle where video used to be

Full disclosure: I shared the same steps in https://bugs.webkit.org/show_bug.cgi?id=230922 cause I don't know if the two bugs are related.
Comment 3 Brent Fulgham 2022-02-12 19:34:29 PST
This should now be fixed in iOS 15.3