加载含WebView布局时Chrome崩溃，logcat报权限拒绝错误求助

Hey Jerry, let's break down this WebView crash issue you're encountering. That webview_zygote32: Failed to make and chown /acct/uid_99009: Permission denied log is a key hint pointing to a sandbox or permission conflict with the WebView zygote process. Here are actionable steps to diagnose and fix it:

1. Check for Shared User ID or Unusual Manifest Configurations #

• First, look for the android:sharedUserId attribute in your AndroidManifest.xml. If it's present, remove it immediately. Shared user IDs can clash with WebView's sandboxed permission model, leading to this exact permission denied error.
• While you've added INTERNET permission, try adding android.permission.ACCESS_NETWORK_STATE as well. WebView sometimes relies on this to handle network state changes, which might indirectly resolve sandbox permission issues.

2. Adjust WebView Initialization and Rendering Settings #

• Try initializing WebView configurations before calling setContentView(), or disable hardware acceleration for the WebView if it's enabled:

  // Add this before setContentView(R.layout.activity_main);
  if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
      WebView.enableSlowWholeDocumentDraw();
  }
  

  Alternatively, add android:hardwareAccelerated="false" to the WebView element in your layout XML.
• Temporarily comment out any custom WebViewClient or WebChromeClient implementations and use the default ones. This helps rule out conflicts introduced by your custom code.

3. Clear WebView Cache and App Data #

• Permission issues often stem from corrupted cache directories. Go to your emulator's Settings > Apps > [Your App] > Storage > Clear Data to wipe all app-related data, including WebView cache.
• You can also programmatically clear WebView cache before loading:

  WebView webView = findViewById(R.id.your_webview_id);
  webView.clearCache(true);
  webView.clearHistory();
  

• Uninstall and reinstall your app to ensure no residual configuration or cache files are left behind.

4. Verify Target SDK and WebView Version Compatibility #

• Check your build.gradle (Module level) for targetSdkVersion. If it's set to 30 or higher, Android 10+'s scoped storage rules might interfere with WebView's sandbox access. Ensure you've handled storage permissions correctly if your app interacts with external storage.
• Update the WebView component in your emulator: Open Chrome in the emulator, go to Settings > About Chrome and install any available updates. Outdated WebView versions often have sandbox permission bugs.
• Test your app on a different AVD with a lower Android version (e.g., Android 10 instead of Android 11) to see if the issue is version-specific.

5. Compare with Working New Project #

Since your new project works on the same AVD, compare the two projects to spot differences:

• Check build.gradle values: compileSdkVersion, minSdkVersion, targetSdkVersion, and any third-party dependencies. A conflicting library might be causing the issue.
• Verify signing configurations: Your current project might be using a custom debug/release signature, while the new project uses the default debug keystore. Try switching to the default keystore for your current project.

If none of these steps resolve the issue, try migrating your WebView-related code to a new blank module in your project, then gradually add other components. This will help you isolate exactly which part of your code or configuration is triggering the conflict.

内容的提问来源于stack exchange，提问作者Jerry Jiang