Skip to content
Latchkey

Google Play Developer API "has not been used or is disabled" in CI

supply called the Google Play Android Developer API but it is not enabled on the Google Cloud project that owns the service account. Until the API is enabled, every request returns an accessNotConfigured error with a link to enable it.

What this error means

supply fails with "Google Api Error: accessNotConfigured: Google Play Android Developer API has not been used in project NNN before or it is disabled". Authentication is fine; the API itself is off.

Play Developer API
[!] Google Api Error: accessNotConfigured: Google Play Android Developer API has not been
used in project 1234567890 before or it is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/androidpublisher.googleapis.com/overview?project=1234567890

Common causes

The Android Publisher API is disabled on the project

The Cloud project that the service account belongs to has never enabled androidpublisher.googleapis.com.

The service account links to the wrong project

The JSON key belongs to a different project than the one where the API is enabled, so the enabled state does not apply.

How to fix it

Enable the Android Publisher API

  1. Open the link in the error or the Cloud Console API library for that project.
  2. Enable Google Play Android Developer API.
  3. Wait a few minutes for propagation, then re-run supply.
Terminal
gcloud services enable androidpublisher.googleapis.com --project=1234567890

Confirm the key matches the enabled project

Ensure the service account JSON key is from the same project where you enabled the API, and that it is linked under Play Console, Setup, API access.

How to prevent it

  • Enable androidpublisher.googleapis.com when provisioning the service account.
  • Keep the service account, key, and enabled API in one project.
  • Document which Cloud project backs Play publishing.

Related guides

Tired of flaky CI? Latchkey auto-heals failed jobs and retries them for you. Start free →