Google Drive Picker搜索无结果且报内部错误的求助

I’ve encountered this exact issue with the Google Picker API before, so let’s break down what’s happening and how to resolve it.

Where does filterTeamDriveResults come from? #

This parameter is tied to Google Shared Drive (previously Team Drive) filtering. The Picker automatically injects it into the pvr endpoint request when:

• Your app requests scopes that include Shared Drive access (like the broad drive.readonly scope)
• The user has access to Shared Drives in their Google account
• The picker view you’re using (e.g., google.picker.ViewId.DOCS) implicitly includes Shared Drive content

As you noted, the official JavaScript API doesn’t expose any direct setting to toggle this parameter—frustrating, I know.

Workaround: Intercept and modify the Picker request #

Since we can’t control this via the official API, we can intercept the XMLHttpRequest sent to the picker/pvr endpoint and strip out the problematic parameter before it’s sent. Here’s a reliable way to do that:

Add this code before you initialize your Google Picker instance:

// Save a reference to the original XMLHttpRequest methods
const originalOpen = XMLHttpRequest.prototype.open;

XMLHttpRequest.prototype.open = function(method, url) {
  // Target only the Picker's pvr endpoint
  if (url.includes('docs.google.com/picker/pvr')) {
    const originalSend = this.send;
    this.send = function(body) {
      if (body) {
        // Parse the URL-encoded request body
        const params = new URLSearchParams(body);
        if (params.has('options')) {
          let options = JSON.parse(params.get('options'));
          // Remove the parameter causing the internal error
          delete options.filterTeamDriveResults;
          // Update the options in the request parameters
          params.set('options', JSON.stringify(options));
          // Replace the original body with the modified version
          body = params.toString();
        }
      }
      // Send the modified request
      originalSend.call(this, body);
      // Restore the original send method to avoid affecting other requests
      this.send = originalSend;
    };
  }
  // Proceed with the original open call
  originalOpen.apply(this, arguments);
};

Key notes for this workaround: #

• Make sure this code runs before you call new google.picker.PickerBuilder().build()—otherwise, the Picker will have already sent requests before the interceptor is active.
• This is a bit of a hack, so keep an eye on future Google Picker API updates (they might change the request structure, which would break this).
• Test with both users who have Shared Drive access and those who don’t to ensure it works consistently.

Alternative: Restrict your API scopes #

If your app doesn’t need access to Shared Drives, try switching to a more limited scope like https://www.googleapis.com/auth/drive.file instead of drive.readonly. This might prevent the Picker from adding the filterTeamDriveResults parameter in the first place, since it won’t have permission to access Shared Drive content.

Here’s how you’d load the API with the restricted scope:

gapi.load('picker', {
  callback: onApiLoad,
  clientId: 'YOUR_CLIENT_ID',
  scope: 'https://www.googleapis.com/auth/drive.file'
});

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