Google Drive Connector linked but no tools visible (EEA, iOS, GPT-5)

ChatGPT Bugs
,
1

After reconnecting the official Google Drive connector, OAuth authentication completes successfully and the connector appears as “linked,” but no Drive tools become available to the model (no search, read_file, or list_files endpoints are registered).

Steps to reproduce:

  1. Using the iOS ChatGPT app (latest version, GPT-5 model, Plus plan, region: EU/EEA).

  2. Enable Connectors under Settings → Beta Features.

  3. Connect Google Drive and complete OAuth login.

  4. Verify: connection succeeds, but the Drive toolset does not load (verified via api_tool.list_resources).

  5. Restarting the app, toggling Connectors, or reconnecting Google Drive does not fix it.

Expected behavior:
After successful OAuth, the Drive endpoints (search, open, read, etc.) should be registered and callable.

Actual behavior:
No endpoints are exposed — the connector shows as linked but remains inert.

Additional info:

  • Other connectors (Gmail, Slack, GitHub) show the same pattern intermittently.

  • Behavior reproducible on multiple EEA accounts.

  • Likely a registry or permissions propagation issue between OAuth and tool activation layers.

Please confirm whether this is a known issue or an intentional regional restriction, and when a fix can be expected.