Daily Keyframes are byte-sized tips from our engineers. We hope they help you remove roadblocks so you can focus on building.
When Apple announced, in iOS 14.3, that WKWebView would have support for navigator.mediaDevices.getUserMedia, we were ecstatic. It meant that iOS applications which relied on a webview could now use audio and video devices, a crucial element for an audio or video call. We were so excited, in fact, that we built Party Line.
However, in the course of development we quickly realized there was a known bug. navigator.mediaDevices.getUserMedia would only work if the HTML file in question was loaded via http(s) origins. If you were loading a local HTML file (using file://), getUserMedia would be denied. Luckily this has been fixed, but those fixes can take time to land, and even longer for users to upgrade to the latest OS version.
So what can be done to get around this today?
The easiest thing to do is host your file somewhere that serves it via https (might as well keep it secure, while we’re at it). If you already have a server for your static assets, simply add it there and you’re good to go. If you don’t, and you want an easy solution, Netlify is a great modern platform for static file deployments (among other things) and even has a drag and drop feature. For Party Line, our iOS HTML file is deployed alongside our React web app, which makes it publicly accessible at https://partyline.daily.co/ios-bridge.html.
To use it in our iOS app, we reference it in Client.swift with the following code:
private static var pageURL: URL {
URL(string: "https://partyline.daily.co/ios-bridge.html")!
}
And then load it in Client.swift with the following code:
let pageURL = Self.pageURL
self.webView.load(URLRequest(url: pageURL))
And that’s it!
If you want to read more about this, check out our html file, and these related tickets:
- https://openradar.appspot.com/48813943 (rdar://48813943)
- https://bugs.webkit.org/show_bug.cgi?id=208667
- https://bugs.webkit.org/show_bug.cgi?id=188360
- https://bugs.chromium.org/p/chromium/issues/detail?id=752458
And if you’re curious about what we built, head over to the repo or read the blog post.
Top comments (0)