Android WebView应用无法下载S3存储桶图片问题求助

Hey Frank, let's troubleshoot why your Android WebView's S3 image download stopped working out of the blue—since the browser version still works perfectly, the issue is definitely rooted in your app's implementation. Let's break down the most likely culprits and fixes based on your code and logcat output:

1. Missing Critical Request Headers (The #1 Suspect) #

Your browser sends all necessary headers (like User-Agent, Referer, or auth-related metadata) with every download request. But when you use DownloadManager, you're spinning up a brand new request that doesn't carry over any of these headers from the WebView. S3 often blocks such requests because they lack the validation metadata it expects.

Quick Fix: Add the WebView's User-Agent to Your Download Request #

Modify your DownloadManager.Request to include the exact same User-Agent string that your WebView uses:

// Grab the WebView's User-Agent
String webViewUserAgent = turbolinksView.getWebView().getSettings().getUserAgentString();
// Attach it to the download request
request.addRequestHeader("User-Agent", webViewUserAgent);

If your S3 bucket uses hotlink protection, add the Referer header matching your web domain too:

request.addRequestHeader("Referer", "https://your-apps-web-domain.com"); // Replace with your actual domain

2. Expired or Stale S3 Signed URLs #

S3 signed URLs have a built-in expiration time (set by your web app when generating the URL). If your app is caching an old URL or reusing one that's since expired, the download will fail. The browser probably fetches a fresh signed URL every time you click download, which is why it works.

Fix: Ensure You're Using a Fresh Signed URL #

Test the URL from your onDownloadStart callback by pasting it into a private browser window—if it fails to load, the URL is expired. Update your web app to generate a new signed URL each time the download button is clicked, so the WebView gets a valid link every time.

3. Fixing the mConsumerName == NULL Logcat Error #

That weird log line suggests your DownloadManager request is missing identifying metadata, which can cause system-level hiccups. Add some context to the request to resolve this:

request.setTitle(filename); // Name of the file being downloaded
request.setDescription("Downloading image from Your App"); // Brief description

This gives the system a clear "consumer name" to associate with the download, fixing the null error.

4. Runtime Permission Checks (For Android 6.0+) #

Even if you have WRITE_EXTERNAL_STORAGE in your AndroidManifest.xml, devices running Android 6.0 (API 23) or higher require you to request this permission at runtime. If your app hasn't done this, the DownloadManager will fail silently (or throw obscure errors).

Fix: Add a Permission Check Before Downloading #

Update your code to check for the permission before triggering the download:

// Check if we have write permission first
if (ContextCompat.checkSelfPermission(this, Manifest.permission.WRITE_EXTERNAL_STORAGE) != PackageManager.PERMISSION_GRANTED) {
    // Request the permission
    ActivityCompat.requestPermissions(this, new String[]{Manifest.permission.WRITE_EXTERNAL_STORAGE}, 1001);
    return;
}

// If permission is granted, proceed with the download logic...

Then handle the permission result to retry the download if the user approves:

@Override
public void onRequestPermissionsResult(int requestCode, @NonNull String[] permissions, @NonNull int[] grantResults) {
    super.onRequestPermissionsResult(requestCode, permissions, grantResults);
    if (requestCode == 1001 && grantResults.length > 0 && grantResults[0] == PackageManager.PERMISSION_GRANTED) {
        // You'll need to store the download parameters (url, userAgent, etc.) temporarily to retry here
        Toast.makeText(this, "Permission granted—retrying download!", Toast.LENGTH_SHORT).show();
    }
}

5. Verify S3 CORS Configuration #

Sometimes S3's CORS policy blocks requests from WebViews even if browsers are allowed. Double-check your bucket's CORS settings to ensure it allows GET requests from your app's User-Agent or origin.

Example CORS Policy for S3 #

<CORSConfiguration>
  <CORSRule>
    <AllowedOrigin>*</AllowedOrigin> <!-- Restrict this to your domain if possible for security -->
    <AllowedMethod>GET</AllowedMethod>
    <AllowedHeader>*</AllowedHeader>
  </CORSRule>
</CORSConfiguration>

Updated onDownloadStart Implementation #

Putting all these fixes together, your updated download listener might look like this:

@Override
public void onDownloadStart(String url, String userAgent, String contentDisposition, String mimeType, long contentLength) {
    // Check runtime permission first
    if (ContextCompat.checkSelfPermission(MainActivity.this, Manifest.permission.WRITE_EXTERNAL_STORAGE) != PackageManager.PERMISSION_GRANTED) {
        ActivityCompat.requestPermissions(MainActivity.this, new String[]{Manifest.permission.WRITE_EXTERNAL_STORAGE}, 1001);
        return;
    }

    String filename = URLUtil.guessFileName(url, contentDisposition, mimeType);
    DownloadManager.Request request = new DownloadManager.Request(Uri.parse(url));
    
    // Add WebView's User-Agent to match browser requests
    String webViewUserAgent = turbolinksView.getWebView().getSettings().getUserAgentString();
    request.addRequestHeader("User-Agent", webViewUserAgent);
    
    // Add Referer header if your S3 bucket uses hotlink protection
    request.addRequestHeader("Referer", "https://your-web-domain.com");
    
    // Fix mConsumerName null error by adding request metadata
    request.setTitle(filename);
    request.setDescription("Downloading image");
    
    request.allowScanningByMediaScanner();
    request.setNotificationVisibility(DownloadManager.Request.VISIBILITY_VISIBLE_NOTIFY_COMPLETED);
    request.setDestinationInExternalPublicDir(Environment.DIRECTORY_DOWNLOADS, filename);
    
    DownloadManager dm = (DownloadManager) getSystemService(DOWNLOAD_SERVICE);
    dm.enqueue(request);
    Toast.makeText(getApplicationContext(), "Download started", Toast.LENGTH_LONG).show();
}

Start with the User-Agent and permission checks first—those are the most common fixes for this exact scenario. If that doesn't resolve it, move on to verifying the signed URL and S3 CORS settings.

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