Description
Hi, I have read the code of the new ipfs-utils/src/support.js. I found a problem below:
getUserMedia is not supported in Chrome on IOS, because of WkWebview in IOS. But in some case, we don’t use getUserMedia function, but just want to use WebRTC for text message. So if use the support.js, some application will not work on chrome in IOS. Maybe we should consider to relaxation of conditions for checking WebRTC support?
P.S there is a reply on stack overflow:
WebRTC has three main JavaScript APIs:
- MediaStream (aka getUserMedia)
- RTCPeerConnection
- RTCDataChannel
For apps running inside Safari App, iOS11+, all WebRTC APIs are supported. That includes getUserMedia
. Be sure to use adapter.js library for best compatibility, since each browser - including Safari - uses a different name for its implementation. For example, in Safari it's navigator.mediaDevices.getUserMedia()
.
But, when using WKWebView or SFSafariViewController , it's a different story:
- Both
RTCPeerConnection
andRTCDataChannel
are supported and working. getUserMedia
is not supported yet, for "security reasons". It most probably won't be available before the next major OS release, which would be iOS 12 in September 2018.
You can still stream video & audio from local storage or consume live media captured by a peer. Hopefully in iOS 12 we'll see some progress...