Bug 212669
| Summary: | Safari users cannot hear remote audio, even though audio track is present | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Feross Aboukhadijeh <feross> |
| Component: | WebRTC | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Critical | CC: | ianbonner, kpd400, mjs, webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 13 | ||
| URL: | https://virus.cafe | ||
Feross Aboukhadijeh
In Safari iOS, the audio for remote streams doesn't work sometimes. The audio track is being sent in the SDP but there's no audio when I add the stream to a <video> tag. This happens 20% of the time and it's very perplexing.
What's super weird is that if I connect the iPhone to debug the Safari tab, and I select the remote video element, and then I run $0.pause(); $0.play() the audio suddenly starts working. Somehow the audio track is present but the video tag is glitching and not playing it, it seems.
I wait for both 'track' events (one for video, one for audio) then I set `video.srcObject = stream`. Very basic WebRTC usage.
I can reproduce this after about 5 tries on the site I'm building, https://virus.cafe, between iOS on the one side and desktop Safari/Chrome on the other.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/63902457>
Feross Aboukhadijeh
Possibly related to https://bugs.webkit.org/show_bug.cgi?id=198545
youenn fablet
Feross, thanks for the report.
Can you try the latest iOS beta to see if that fixes your issue?
Feross Aboukhadijeh
Hi youenn, I will get an extra iOS device to install the iOS beta onto and then report back what I find. Thanks!
Maciej Stachowiak
I tried this on the iOS beta but I couldn't get a conversation partner so could not confirm if fixed or not.
Kyle Dunn
I tested with iOS 13.6 beta 3 and can confirm the fix. Like Feross I was previously reproducing the bug in 13.5 about 20% of the time.
youenn fablet
Closing as per above comments, please reopen if needed.
Feross Aboukhadijeh
The issue seems fixed in the iOS 14 beta.
Ian Bonner
We have been experiencing a very similar issue and have been monitoring this bug. Is this expected to be closed in the ios 13.6 release or just the ios 14 release? The response from Feross indicates it is resolved in ios 14 but I was hoping for confirmation of a resolution in the ios13.6. Thanks
Kyle Dunn
(In reply to Ian Bonner from comment #9)
> We have been experiencing a very similar issue and have been monitoring this
> bug. Is this expected to be closed in the ios 13.6 release or just the ios
> 14 release? The response from Feross indicates it is resolved in ios 14 but
> I was hoping for confirmation of a resolution in the ios13.6. Thanks
It's fixed in the latest 13.6 beta so I think it's safe to assume it will be fixed in the general public release of 13.6 soon.