-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reduce strictness of WebRTC support check #50
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
no one notice me? |
I guess it depends on what What do you think @hugomrdias? |
IPFS' use of WebRTC is only as a data channel, we don't use getUserMedia and sometimes the user has restricted access to this API so add a 'supports' test that is just for data channels. Fixes #50
The use of WebRTC in IPFS is only as a data channel, we don't use getUserMedia and sometimes the user has restricted access to this API so add a 'supports' test that is just for data channels. Fixes #50
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:
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'snavigator.mediaDevices.getUserMedia()
.But, when using WKWebView or SFSafariViewController , it's a different story:
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...
The text was updated successfully, but these errors were encountered: