Gemini Login Not Working — Fix Google AI Sign-In Issues

Overview

Gemini login failures fall into three distinct buckets: web UI sign-in problems at gemini.google.com, mobile app authentication on Android/iOS, and API/OAuth issues for developers using the Gemini API. Each has different root causes and different fixes.

The frustrating part: Google’s error messages rarely distinguish between “your account can’t access Gemini” and “something broke during authentication.” You get a generic redirect loop or a blank screen, and you’re left guessing. This guide separates the causes by platform so you can skip to what actually applies.

Symptoms

Login failures present differently depending on platform:

Web (gemini.google.com):
– Redirect loop between accounts.google.com and gemini.google.com
– Blank white page after selecting your Google account
– “Something went wrong” with no error code
– Page loads but shows “Gemini isn’t available for this account”
– Stuck on the Google account picker — selecting an account does nothing

Mobile app (Android/iOS):
– App opens to a sign-in screen that won’t accept your account
– “Can’t connect” or “Network error” after tapping your account
– App crashes immediately after authentication attempt

API/Developer:
– 401 Unauthorized or 403 Forbidden from the Gemini API
– OAuth consent screen won’t load or returns an error
– API key works in AI Studio but fails in your application

Why This Happens

Gemini’s login depends on Google’s standard OAuth infrastructure, but it adds its own access-control layer on top. That creates multiple failure points.

Account eligibility is the most common cause. Gemini may not be available in every country, for every Google account type, or for every Workspace configuration. Google doesn’t publish an exhaustive list of restrictions, so the only reliable test is trying a different account.

Browser state corruption is second. Gemini’s web app is a single-page application that stores session tokens in cookies and local storage. When these get out of sync — often after a Chrome update, switching between multiple Google accounts, or an extension interfering — the auth flow breaks without a clear error.

API authentication fails for different reasons: expired keys, project-level API restrictions, or billing issues on the Google Cloud project tied to the key.

Verify Account Eligibility and Service Status

Start here because no amount of cache-clearing fixes an account that doesn’t have access.

1. Open Google Cloud Status Dashboard and check for incidents affecting “Generative AI” or “Google Workspace” services.
2. Try signing in at gemini.google.com with a personal Gmail account (not Workspace). If personal works but Workspace doesn’t, the issue is admin-side.
3. Check your account’s country/region. Open myaccount.google.com → Personal info → look at your registered country.
4. If you’re on a Workspace account, ask your admin to verify that Gemini is enabled under Admin console → Apps → Google Workspace → Gemini.

# Quick eligibility check — open in browser console on gemini.google.com
# If this returns a 401 or 403, your account lacks access
fetch('/api/check').then(r => console.log(r.status))

The Workspace gotcha nobody mentions: Even if your Workspace admin has enabled Gemini, it may only be enabled for specific organizational units. If you were recently moved between OUs (common during reorgs), your access may have silently changed. The admin needs to check the OU-level setting, not just the top-level toggle.

Fix Browser-Level Authentication Issues

Browser fixes, in order from least to most disruptive:

Why incognito isn’t always the answer: Incognito mode disables third-party cookies by default in recent Chrome versions. Gemini’s auth flow involves cross-domain cookies between google.com subdomains. If incognito works, it proves the issue is cached state — but if it doesn’t work, it may be the cookie restrictions, not a deeper problem.

Browser-Specific Notes

Safari: Intelligent Tracking Prevention (ITP) aggressively blocks cross-site cookies. If Gemini fails in Safari but works in Chrome, go to Safari → Settings → Privacy → uncheck “Prevent cross-site tracking” temporarily.

Firefox: Enhanced Tracking Protection’s “Strict” mode breaks Google’s auth redirects. Switch to “Standard” under Settings → Privacy & Security.

Edge: The “Efficiency mode” sleeping tab feature can break background auth token refresh. Exclude gemini.google.com from sleeping tabs.

Fix Mobile App Login Failures

Android

1. Force stop the Gemini app: Settings → Apps → Gemini → Force Stop. Don’t just swipe it away — that doesn’t fully kill the process on most Android skins.
2. Clear app cache (not data): Settings → Apps → Gemini → Storage → Clear Cache. Clearing data resets the app entirely; try cache first.
3. Check Google Play Services: Gemini depends on Play Services for authentication. Go to Settings → Apps → Google Play Services → check for updates.
4. Verify the correct Google account is primary: Settings → Accounts. The Gemini app authenticates against the device’s primary Google account by default.

iOS

1. Force quit: Swipe up from the app switcher.
2. Check iOS version: The Gemini app may require a minimum iOS version. Check the App Store listing for requirements.
3. Re-authenticate your Google account: Settings → scroll to the Gemini app → check account permissions. Alternatively, remove and re-add your Google account under Settings → Mail → Accounts.

Fix API and Developer Authentication Issues

If you’re hitting 401 or 403 errors from the Gemini API, the web UI login flow is irrelevant. API auth is a separate system.

API Key Issues

# Test your API key directly
curl -s "https://generativelanguage.googleapis.com/v1/models?key=YOUR_KEY" \
  | head -20

Common API key failures:

• Key restricted to wrong APIs: In Google Cloud Console → Credentials → click your key → check “API restrictions.” The key must include “Generative Language API.”
• Key restricted to wrong IPs or referrers: Same screen, check “Application restrictions.”
• Project billing disabled: The Cloud project tied to the key needs an active billing account, even for free-tier usage.
• Key regenerated but old key cached in code: Environment variables, .env files, or CI/CD secrets may still hold the old key.

OAuth / Service Account Issues

# Verify service account permissions
gcloud auth list
gcloud services list --enabled | grep generativelanguage

If generativelanguage.googleapis.com doesn’t appear in the enabled services list, enable it:

gcloud services enable generativelanguage.googleapis.com

The quota trap: Even with a valid key, you may get 429 Too Many Requests that looks like an auth error in some client libraries. Check your quota at Cloud Console → APIs & Services → Generative Language API → Quotas.

Handle Multi-Account and Workspace Conflicts

Google’s multi-account handling is the single most common cause of “login works everywhere except Gemini” problems. Here’s why.

Google assigns each signed-in account an index (authuser=0, authuser=1, etc.). Gemini sometimes redirects to authuser=0 regardless of which account you selected. If your Gemini-enabled account is authuser=1, the redirect sends you to the wrong account.

Fix:

1. Sign out of all Google accounts (this is the one exception to the “don’t sign out” advice above — multi-account conflicts require it).
2. Sign in to your Gemini-enabled account first — this makes it authuser=0.
3. Then sign into other accounts.

Alternatively, bookmark https://gemini.google.com/?authuser=1 (or whichever index matches your target account) to force the correct account.

Workspace vs. Personal Account Precedence

If you’re signed into both a Workspace and personal account, Gemini may default to whichever account was signed in first, not whichever you selected. This is especially confusing because the account picker shows you selecting the right account — but the redirect ignores your choice.

If It Still Fails

If none of the above fixes resolve the issue:

1. Capture the exact error: Open DevTools (F12) → Network tab → reproduce the login attempt → look for the failing request and its response body. Screenshot or copy the full response.
2. Check the browser console: DevTools → Console tab. Look for errors mentioning auth, token, 403, or CSP.
3. Try a completely different device. If login works on another device with the same account, the problem is device-specific. If it fails everywhere, the problem is account-specific.
4. Contact Google support: For Workspace accounts, your admin can open a support ticket. For personal accounts, use the Gemini Help Center. Include the error details from steps 1-2.
5. Check Google’s community forums: Search for your specific error message. Gemini issues often affect many users simultaneously, and workarounds appear in forum threads before official fixes.

FAQ