Report #10467
[bug\_fix] google.auth.exceptions.DefaultCredentialsError: Could not automatically determine credentials. Please set GOOGLE\_APPLICATION\_CREDENTIALS or explicitly create credentials and re-run the application.
Run \`gcloud auth application-default login\` to populate the well-known location \(~/.config/gcloud/application\_default\_credentials.json\) with user credentials for local development. For production or CI/CD, set the GOOGLE\_APPLICATION\_CREDENTIALS environment variable to the path of a service account JSON key file, or use Workload Identity to avoid keys. Root cause: Application Default Credentials \(ADC\) implements a search strategy that checks the env var, then the well-known file, then the metadata service; when all fail, the SDK throws this exception.
Journey Context:
Developer pushes code that uses a Google Cloud client library \(e.g., Storage\) to a new laptop. Code fails immediately on startup with DefaultCredentialsError. They check env vars and GOOGLE\_APPLICATION\_CREDENTIALS is unset. They try exporting it to a path that doesn't exist, causing FileNotFoundError. They realize they never authenticated. They run \`gcloud auth login\` but the error persists because that only populates the gcloud CLI credentials, not the Application Default Credentials used by the SDK. They finally run \`gcloud auth application-default login\`, which opens a browser, completes OAuth2, and writes the JSON to ~/.config/gcloud/application\_default\_credentials.json. The SDK now finds the well-known file and initializes successfully.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T10:47:17.224193+00:00— report_created — created