Gmail API OAuth not showing all requested scopes in consent flow

Other Questions Gmail
1

I’m having trouble with my Google Gmail API OAuth setup. In the Cloud Console, I configured the app with full Gmail scopes. But when I start the OAuth consent process, it only shows read-only options. I can’t find scopes like gmail.labels or gmail.modify.

I know you need to verify apps for some scopes in production. But my app is still in testing mode. So that shouldn’t be the issue, right?

How can I make these extra scopes show up in the consent screen? I need them so my app can set labels on messages.

Here’s a simplified version of what I’m trying to do:

from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build

def set_label(service, msg_id, label_id):
    service.users().messages().modify(userId='me', id=msg_id, body={
        'addLabelIds': [label_id]
    }).execute()

# But I can't get the right scopes to make this work!

Any ideas on how to fix this? It’s driving me crazy!

2

Hey there! I’ve been down this rabbit hole before with Gmail API scopes. Here’s what worked for me:

Double-check your authorization URL. Make sure you’re including ALL the scopes you need, especially gmail.modify and gmail.labels. Sometimes the UI can be misleading.

Also, try revoking your test account’s access and starting fresh. Go to your Google Account settings > Security > Third-party apps with account access. Remove your app and try again.

If that doesn’t work, there might be a delay between updating scopes in the Cloud Console and them showing up in the consent screen. I’ve seen it take up to an hour in some cases.

Lastly, if you’re using a service account, remember they don’t go through the normal OAuth flow. You’d need to set up domain-wide delegation instead.

Hope this helps! Let me know if you need more details on any of these steps.

3

I encountered a similar issue when setting up Gmail API OAuth for a project. The problem might be in how you’re requesting the scopes during the authorization flow. Make sure you’re explicitly including all required scopes in your authorization request, not just relying on what’s in the Cloud Console.

Check your code where you initiate the OAuth flow. You should see something like:

SCOPES = ['https://www.googleapis.com/auth/gmail.modify',
          'https://www.googleapis.com/auth/gmail.labels']

flow = Flow.from_client_secrets_file('path/to/client_secret.json', SCOPES)

If you’re not specifying the scopes this way, the consent screen might default to read-only permissions. Also, double-check that your client_secret.json file is up-to-date and matches your Cloud Console configuration.

Lastly, try clearing your browser cache or using an incognito window when testing. Sometimes old permissions can stick around and cause confusion during development.

4

yo, i had the same headache with gmail api. make sure ur actually requesting ALL the scopes in ur code, not just relying on cloud console settings. also, try using a new google account for testing - sometimes old permissions mess things up. if that dont work, wait an hour or so. google can be slow updating scopes sometimes lol. good luck!