When webrtc connection is established and both ends send and receive audio and video and if remote stream is attached to video element then it has random volume. It is either loud, silent or completly muted. Executing video.srcObject = video.srcObject causes to jump between these volumes. You can try it eg. on https://janus.conf.meetecho.com/videocalltest.html: 1. Join from Safari on iOS 13.3.1, on the other end in my case it was Chrome on Linux but other platforms were reported as well. 2. Audio volume on iPhone is one of 3 mentioned (random) 3. Execute in JS console on iOS Safari: document.getElementsByTagName('video')[1].srcObject = document.getElementsByTagName('video')[1].srcObject; 4. goto 2 Issue can be reproduced also for example on www.gruveo.com.
<rdar://problem/59751337>
I also found the same problem in my product, a web-conference application for medical devices. (it can be easily reproduced in WebRTC sample pages, https://webrtc.github.io/samples, as well. The volume control of WebRTC in Safari browser version 13 for iPhone and iPad is totally out of control. Is there any workaround to avoid this problem?
Does anyone know how to determine if/when Apple will fix this? This is a complete nightmare for anyone trying to use WebRTC audio/video calls :-(
Symptoms seems to be same as in https://bugs.webkit.org/show_bug.cgi?id=198545 *** This bug has been marked as a duplicate of bug 198545 ***
Reopening as this probably requires a dedicated solution.
We are seeing 2 issues with iOS 13.3.1. Participant A on iPhone 11 with iOS 13.3.1 and participant B on IE(Electron). 1. Participant A on iPhone can't hear participant B after WebRTC connection is established. Mobile browser refresh on iPhone is resolving it. 2. Participant B on IE can't hear participant A on iPhone after WebRTC connection is established. Mobile browser refresh on iPhone is NOT resolving it. This issue is causing lots of user dissatisfaction. Will the fix of 208134 resolve both conditions? Is there any update on fix timeline?
https://bugs.webkit.org/show_bug.cgi?id=211287 seems to help as well.
Please test it on latest iOS 13.5.5 beta *** This bug has been marked as a duplicate of bug 211287 ***