Post

Replies

Boosts

Views

Activity

WebRTC IceCandidates seems weird
Hi there, I'm currently making a web application using webRTC. Even though all the SDP info and ICES of caller, callee are well transmitted, the connection was kept failing. The other devices are functioning well. However at just Iphone(13), it's not working. I tried to connect at same network. And it's working. Therefore I think it's a problem about Ice candidates. I read similar post to avoid this issue. And when one of safari's advanced option called WebRTC platform UDP sockets is disabled it's working. Is there a way that I can connect without tuning options of Safari? Thanks. FYI this is one of my Iphone's Ice candidate:842163049 1 udp 1685921535 118.235.10.100 50750 typ srflx raddr 0.0.0.0 rport 50750 generation 0 ufrag 7e7f network-id 3 network-cost 900
0
1
532
Aug ’23
iOS 16.7.2, iOS 17.1.1: navigator.permissions.query permissionStatus inconsistent response
I am developing a web application that uses the camera and microphone. As part of this, I need to ask for camera and microphone permissions and also handle changes in these permissions. However, a few issues were discovered in Chrome on iPhone and iPad. The issue I encountered is that, after attaching an onchange event listener to the status obtained from navigator.permissions.query({name: "microphone"}), there was no detected change in permission state even after camera and microphone permissions were granted. However, when I directly executed navigator.permissions.query({name: "microphone"}) in the Safari JavaScript console, it showed a different state value compared to the status object I created. The status object continuously displayed "prompt", while the direct console query showed "granted". I suspect that the status object is not being updated in real-time with the browser, or there might be a bug since the onchange event was added quite recently (around September 2022, as far as I know). Is anyone experiencing similar issues, or does anyone know how to resolve this problem? Below is a list of the devices I have tested with. iPhone: iPhone 13 iOS 16.7.2 (maybe safari version is same) agent AppleWebKit 605.1.15 criOS 119.0.6045.169 Mobile 15E148 Safari 604.1 chrome version 119.0.6045.169(official build) iPad: iPad Air 4th iOS 17.1.1 (maybe safari version is same) agent AppleWebKit 605.1.15 criOS 119.0.6045.169 Mobile 15E148 Safari 604.1 chrome version 119.0.6045.169(official build)
0
2
983
Dec ’23