Bug 211829 – WebRTC Audio fail to capture from lock screen in Safari

• Status: RESOLVED
• Resolution: CONFIGURATION CHANGED
• Component: WebRTC

[Vicky Cen]

Steps to reproduce:

1. On an iPad, go to https://webrtc.github.io/samples/
2. Lock the screen manually and wait for 5 seconds
3. Unlock the screen and select sample "Audio-only getUserMedia() output to local audio element" from the tab.
4. Make a pop sound and you can't hear yourself.
5. Refreshing the page you can't still hear the sound. Only after you restart safari or manually open a new tab with "Audio-only getUserMedia() output to local audio element", the sound will work for you.

It's happening on iPad with IpadOs 13.2.2 and iPhone 6s with IOS13.3.1

[Radar WebKit Bug Importer]

<rdar://problem/63205337>

[Vicky Cen]

This is affecting our web application. When a 2-way webrtc call is established, if 1 party is using iPhone / iPad, and joins the call after unlock the screen and from an existing tab in safari, this party's audio is not sent, so the other party cannot hear iPhone / iPad user but video track works well. When this issue happens, checking peerconnection.getStats() for iPhone / iPad user, the audio.sent.bytessent is 0. 
Restart Safari or joins the call by opening a tab (clicking the "+" in safari to open a tab) can solve this problem. 

This is making an impact on our product as our customers don't understand the workaround and report it as a critical issue to us. 

Are there any other workaround / solutions before this is fixed? Or is there any timing for the fix?

[Brent Fulgham]

This is actually:
<rdar://60486776>

[Brent Fulgham]

This issue was fixed by Bug 209411 and Bug 209412.

[Brent Fulgham]

These fixes should be in shipping releases.