continuedev / continuedev/continue

Error: Gemini 3.1 Pro - Unknown error

Open
#12,781 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:integration kind:bug stale
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Error Details

Model: Gemini 3.1 Pro
Provider: gemini
Status Code: N/A

Error Output

{"error":{"message":"{\n  \"error\": {\n    \"code\": 403,\n    \"message\": \"Requests to this API generativelanguage.googleapis.com method google.ai.generativelanguage.v1beta.GenerativeService.StreamGenerateContent are blocked.\",\n    \"status\": \"PERMISSION_DENIED\",\n    \"details\": [\n      {\n        \"@type\": \"type.googleapis.com/google.rpc.ErrorInfo\",\n        \"reason\": \"API_KEY_SERVICE_BLOCKED\",\n        \"domain\": \"googleapis.com\",\n        \"metadata\": {\n          \"consumer\": \"projects/177838813423\",\n          \"service\": \"generativelanguage.googleapis.com\",\n          \"apiName\": \"generativelanguage.googleapis.com\",\n          \"methodName\": \"google.ai.generativelanguage.v1beta.GenerativeService.StreamGenerateContent\"\n        }\n      },\n      {\n        \"@type\": \"type.googleapis.com/google.rpc.LocalizedMessage\",\n        \"locale\": \"en-US\",\n        \"message\": \"Requests to this API generativelanguage.googleapis.com method google.ai.generativelanguage.v1beta.GenerativeService.StreamGenerateContent are blocked.\"\n      }\n    ]\n  }\n}\n","code":403,"status":"Forbidden"}}

Additional Context
Please add any additional context about the error here

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the report. Start by reproducing the Gemini 3.1 Pro request and checking the reported 403 API_KEY_SERVICE_BLOCKED response, then determine whether the failure is in the Gemini provider integration or API-key service permissions. Done means the cause and a reproducible resolution are documented.

Written by the indexing model from the issue text.

Assessment

Domain
ai, api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.