WebRTC in iOS 14.3 is not working

[Faiizii]

• I have read the README
• I have already searched for the same problem
• I have read and done the setup for Android: IMPORTANT Note for Android and iOS and IMPORTANT Note for Android
• I have read and done the setup for iOS: IMPORTANT Note for Android and iOS and IMPORTANT Note for iOS
• I have ran the sample app and it does not work there

Environment

Technology	Version
Flutter version	1.22.5 stable channel
Plugin version	4.0.0+4
Android version
iOS version	14.3
Xcode version	12.3

Device information:

Description

Expected behavior:
Create the call as it is doing in https://webrtc.github.io/test-pages/src/iframe-apprtc/ and the app is perfectly working in android as expected.
Current behavior:
But the web view is saying the unable to get access of user media and unable to create RTC peer connection.

Steps to reproduce

InAppWebView( 
                initialUrl: callUrl,
                initialOptions: InAppWebViewGroupOptions(
                  crossPlatform: InAppWebViewOptions(
                      mediaPlaybackRequiresUserGesture: false,
                      debuggingEnabled: true,
                      clearCache: true,
                      javaScriptEnabled: true,
                      preferredContentMode: UserPreferredContentMode.MOBILE
                  ),
                ),
                onWebViewCreated: (InAppWebViewController controller) {
                  //web view created
                },
                androidOnPermissionRequest: (InAppWebViewController controller, String origin, List<String> resources) async {
                  print('resource list : ${resources.toString()}'); // allready allowed the camera and microphone permission
                  return PermissionRequestResponse(resources: resources, action: PermissionRequestResponseAction.GRANT);
                }
            )

[pichillilorenzo]

Please see my comment here on how to setup WebRTC on iOS 14.3+ #200 (comment)

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug and a minimal reproduction of the issue.