You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 between iOS on the one side and desktop Safari/Chrome on the other.
Hi @feross! Safari team from Apple communicated that the issue is fixed in the latest iOS beta 13.5.5, which is available for testing with the iOS dev account.
Our internal testing confirmed the fix. Any chance you could verify on your end?
I am still not able to get iphones to play any sound in voice chats. PC users can hear them, the peers are established fine, but iphone users cannot hear anything.
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
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 between iOS on the one side and desktop Safari/Chrome on the other.
This may be a bug in Safari's WebRTC or audio stack so I reported it here: https://bugs.webkit.org/show_bug.cgi?id=212669 just in case.
Anyone else seen this or have ideas?
The text was updated successfully, but these errors were encountered: