[Webkit-unassigned] [Bug 198516] New: Can't capture audio from mic or play through speakers after another app uses devices

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jun 3 22:22:48 PDT 2019


https://bugs.webkit.org/show_bug.cgi?id=198516

            Bug ID: 198516
           Summary: Can't capture audio from mic or play through speakers
                    after another app uses devices
           Product: WebKit
           Version: Safari 12
          Hardware: iPhone / iPad
                OS: iOS 12
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebRTC
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: kentbriggs5 at gmail.com
                CC: youennf at gmail.com

If another application captures devices while a tab is open, that tab won't be able to get sound from the mic or play sound through the speakers. Seems very similar to this bug: https://bugs.webkit.org/show_bug.cgi?id=179964. I've filed a separate bug report because that bug was resolved over a year ago.

Simple repro: https://codepen.io/dbriggs/pen/OYqprv.

These are the steps:
 1. Capture your mic/cam
 2. Stop capturing
 3. Open a different app (I tested with appear.in) and capture your devices in the app.
 4. Stop capturing in the app and return to Safari.
 5. Try capturing again.

Safari will no longer get sound from your mic. Also, it can't play sound through your speakers. I put a simple audio tag on the page with an mp3 file. Before the issue occurs, you'll hear the audio sample if you click the button to play it. Afterwards, you hear nothing. On refresh, the issue persists. You need to open this page in a new tab for it to work again.

You can also perform the steps in a different order and get the same result. For example, you can switch to the other app while you're still capturing and your existing stream won't be getting audio anymore when you return.

I'm getting this on an iPhone 5S running iOS 12.3.1 but not on my iPad Mini 2 running 12.4 (beta). So it's possible that was already resolved in the beta release. If that's the case, feel free to close this.

Potentially related to this bug (https://bugs.webkit.org/show_bug.cgi?id=180748), although it does sound a bit different.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190604/00528070/attachment.html>


More information about the webkit-unassigned mailing list