Bug 221031 - getUserMedia on iOS 14.4 with WKWebView still produces a NotAllowedError
Summary: getUserMedia on iOS 14.4 with WKWebView still produces a NotAllowedError
Status: RESOLVED DUPLICATE of bug 220184
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-27 03:11 PST by Marc Bonsels
Modified: 2021-01-27 06:31 PST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Bonsels 2021-01-27 03:11:08 PST 
I'm trying to use getUserMedia on iOS 14.4 with WKWebView within a Cordova app. I'm using the HelloWorld app from Cordova to reproduce this.

I provided the NSCameraUsageDescription string.

I'm using the sample code as provided on https://webkit.org/blog/11353/mediarecorder-api/ (but with audio set to false).

When I first launch the app and click the button to start the stream, the permission request comes up, which I confirm. Then this error occurs: "NotAllowedError: The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission"

Afterwards the permission request will not come again, only after I re-install the whole app.

Am I doing anything wrong? From what I understood, getUserMedia should be available in iOS 14.4 for apps based on WKWebView, right?
Comment 1 youenn fablet 2021-01-27 06:27:37 PST 
The issue is probably that the domain URL is not HTTP or HTTPS so access is always denied. This is fixed in bug 220184.

*** This bug has been marked as a duplicate of bug 220184 ***
Comment 2 youenn fablet 2021-01-27 06:28:29 PST 
The only workaround for now is to have your content be loaded from a HTTP (localhost)/HTTPS URL.
Comment 3 Marc Bonsels 2021-01-27 06:31:50 PST 
Thanks for the feedback, Youenn.

I saw the bug you referenced, but I thought this was fix was shipped with iOS 14.4, no?