Connecting my application to Google Drive

Other Questions Google drive
1

I’m having trouble getting my app to show up in Google Drive’s ‘Open With…’ menu. I’ve followed the docs and published to test users. Google Drive asked for permission to add my app, but it’s not showing up.

When I check my authorized apps, mine says ‘Disk API’ instead of ‘By file Drive API’ like other working apps.

Here’s my manifest file:

{
  "appName": "MyApp",
  "summary": "App description",
  "version": "1.0.0",
  "manifestVersion": 2,
  "platform": "GOOGLE_DRIVE",
  "projectId": "myproject123",
  "icons": {
    "128": "app_icon.png"
  },
  "application": {
    "endpoints": [
      "https://myapp.example.com"
    ],
    "start": {
      "url": "https://myapp.example.com/editor"
    }
  },
  "supportedFileTypes": {
    "https://drive.google.com/file/open": [
      {
        "formats": ["image/png", "image/jpeg"],
        "link": "https://myapp.example.com/editor",
        "action": "Edit",
        "displayMode": "fullscreen"
      }
    ]
  }
}

Can anyone help me figure out what I’m doing wrong? Thanks!

2

I encountered a similar issue when integrating my app with Google Drive. The key problem seems to be the ‘Disk API’ vs ‘By file Drive API’ discrepancy you mentioned. This often indicates that your app isn’t properly configured to use the Drive API.

To resolve this, double-check your Google Cloud Console settings. Ensure you’ve enabled the Google Drive API specifically, not just general Google APIs. Also, verify that your OAuth consent screen is properly set up with the correct scopes for Drive integration.

Another potential issue could be with your manifest file. Try adding a ‘driveScopes’ field to specify the exact Drive permissions your app needs. For example:

"driveScopes": ["https://www.googleapis.com/auth/drive.file"]

Lastly, remember that changes can take some time to propagate. If you’ve made recent updates, wait a few hours and try again. If the problem persists, review Google’s troubleshooting guide for Drive API integration.

3

As someone who’s gone through the Google Drive integration process, I can relate to your frustration. One thing that stood out to me is the ‘Disk API’ issue you mentioned. This typically happens when the app isn’t correctly set up for Drive API usage.

Have you verified your OAuth 2.0 Client ID settings in the Google Cloud Console? Make sure you’ve selected ‘Web application’ as the application type and added your app’s domain to the authorized JavaScript origins.

Also, double-check your API scopes. You might need to explicitly request the ‘https://www.googleapis.com/auth/drive.file’ scope in your authorization request.

Lastly, I noticed your manifest doesn’t include the ‘driveScopes’ field. Try adding it like this:

driveScopes: ["https://www.googleapis.com/auth/drive.file"]

This explicitly tells Google Drive what permissions your app needs. If none of these solve the issue, you might want to reach out to Google’s support forums for more specialized help.

4

hey there, i had a similar headache with drive integration. make sure ur using the right API in google cloud console. double-check ur OAuth setup too - the scopes gotta match wat ur app needs.

also, try adding ‘driveScopes’ to ur manifest:

"driveScopes": ["https://www.googleapis.com/auth/drive.file"]

if that dont work, hit up google support. they mite spot something we missed. good luck!