技术问询：能否在同一Activity中用WebView打开Chrome Client替代Chrome？

Absolutely—you don’t need to launch the standalone Chrome browser to get Chrome’s WebRTC support in your app. The Android WebView (on modern devices) is built on Chrome’s rendering engine, and by configuring it with a WebChromeClient (instead of just WebViewClient), you can handle all the WebRTC-related functionality directly within your existing Activity.

Here’s how to set this up properly, step by step:

1. Add Required Permissions First #

WebRTC needs access to camera, microphone, and network resources. Add these to your AndroidManifest.xml:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
<uses-feature android:name="android.hardware.camera" />
<uses-feature android:name="android.hardware.camera.autofocus" />

For Android 6.0+, you’ll also need to request these permissions dynamically at runtime before loading your WebRTC page.

2. Configure WebView Settings for WebRTC #

Enable critical settings to support WebRTC features in your WebView:

val webView = findViewById<WebView>(R.id.your_webview_id)
webView.apply {
    // Enable JavaScript (non-negotiable for WebRTC)
    settings.javaScriptEnabled = true
    // Allow media access without requiring a user gesture first (optional but helpful)
    settings.mediaPlaybackRequiresUserGesture = false
    settings.allowFileAccess = true
    settings.allowContentAccess = true
    // Enable hardware acceleration to prevent WebRTC stream lag
    setLayerType(View.LAYER_TYPE_HARDWARE, null)
}

3. Use WebChromeClient to Handle WebRTC Events #

This is the core fix for your WebRTC compatibility issue. WebChromeClient manages browser-level interactions like media permission requests—something WebViewClient can’t handle. Here’s a basic implementation:

webView.webChromeClient = object : WebChromeClient() {
    // Grant camera/microphone permissions requested by the web page
    override fun onPermissionRequest(request: PermissionRequest) {
        // Adjust this to only grant permissions your app actually needs
        request.grant(request.resources)
    }

    // Optional: Handle fullscreen mode if your WebRTC app uses it
    override fun onShowCustomView(view: View?, callback: CustomViewCallback?) {
        // Add your fullscreen logic here (e.g., expand WebView to fill screen)
        super.onShowCustomView(view, callback)
    }

    override fun onHideCustomView() {
        // Clean up fullscreen state when done
        super.onHideCustomView()
    }
}

4. Load Your WebRTC Page #

Finally, load your WebRTC-enabled web page directly into the embedded WebView:

webView.loadUrl("https://your-webrtc-web-app.com")

Key Notes to Avoid Issues #

• WebView Version: Ensure the device has an up-to-date WebView (Android 5.0+ uses Chrome-based WebView by default—prompt users to update if needed).
• Dynamic Permissions: Don’t skip runtime permission requests for CAMERA and RECORD_AUDIO on Android 6.0+—the onPermissionRequest callback won’t work if the app lacks these permissions.
• Why WebChromeClient?: Unlike WebViewClient (which only handles navigation and page loading), WebChromeClient manages media permissions, fullscreen, and other browser UI interactions that WebRTC relies on.

This setup keeps the WebRTC session entirely within your Activity, no external Chrome app launch required—exactly what you need for your development work.

内容的提问来源于stack exchange，提问作者A. Shawkat