decolua/9router · error · Error

No authorization code received

Error message

No authorization code received

What it means

Thrown by AntigravityService.connect when the OAuth callback arrived without an `error` parameter but also without a required `code` parameter. The local callback server captured the redirect, but Google's response carried no authorization code, so the token exchange cannot proceed. Unlike error 244, this is an unexpected/malformed callback rather than an explicit denial.

Source

Thrown at src/lib/oauth/services/antigravity.js:278

        }, 300000);

        const checkInterval = setInterval(() => {
          if (callbackParams) {
            clearInterval(checkInterval);
            clearTimeout(timeout);
            resolve();
          }
        }, 100);
      });

      close();

      if (callbackParams.error) {
        throw new Error(callbackParams.error_description || callbackParams.error);
      }

      if (!callbackParams.code) {
        throw new Error("No authorization code received");
      }

      spinner.start("Exchanging code for tokens...");

      // Exchange code for tokens
      const tokens = await this.exchangeCode(callbackParams.code, redirectUri);

      spinner.text = "Fetching user info...";

      // Get user info
      const userInfo = await this.getUserInfo(tokens.access_token);

      spinner.text = "Loading Code Assist configuration...";

      // Load Code Assist to get project ID and tier
      const { projectId, tierId } = await this.loadCodeAssist(tokens.access_token);

      if (!projectId) {

View on GitHub (pinned to 90b52e06ff)

Solutions

1. Re-run the connect command and complete the Google login in the browser window it opens — don't navigate to the callback URL manually
2. Disable browser extensions/ad-blockers that may strip query parameters and retry
3. Check that no corporate proxy sits between the browser and the localhost callback server
4. If it reproduces, log callbackParams in connect() to see what the callback server actually received

if (!callbackParams.code && !callbackParams.error) {
  throw new Error(`Callback missing both code and error. Received keys: ${Object.keys(callbackParams).join(',')}`);
}

function hasAuthCode(params) { return params != null && typeof params.code === 'string' && params.code.length > 0; }

try {
  await service.connect();
} catch (e) {
  if (e.message === 'No authorization code received') {
    console.error('Callback had no code param. Re-run connect and complete login in the opened browser window.');
  } else throw e;
}

When it happens

Trigger: Callback URL hit directly by the user's browser (manual navigation) with no query params; partial redirects where Google dropped the code; a proxy or browser extension stripping query parameters; state/fragment confusion in custom redirect handling.

Common situations: User bookmarking/pasting the localhost callback URL into a fresh tab; aggressive privacy extensions rewriting the redirect; running the flow behind a corporate proxy that mangles query strings.

Related errors

• No authorization code received
• No authorization code received
• Vertex: failed to mint access token from Service Account JSO
• Vertex: failed to refresh access token from ADC JSON (author
• loadCodeAssist failed: HTTP ${response.status} ${errorText.s

AI-assisted analysis of decolua/9router@90b52e06ff (2026-08-30). Data as JSON: /api/errors/3ba196edc8dbab1f. Report an issue: GitHub.