Status decoded

Android NOT_REGISTERED package remediation guide

NOT_REGISTERED means the queried identity was not found in the official registration record. The cause may be an unfinished console workflow, a wrong package value or a certificate that has not been associated correctly.

Guide summary

Resolve an Android package that the Developer ID Status API does not recognize without changing signing keys unnecessarily.

For: Release owners triaging an unresolved package after the first regional enforcement date.

Release sequence

  1. Confirm the exact production application ID for the store artifact; flavor and debug suffixes can name a different package.
  2. Open the console for the account that distributes the app and inspect its package-registration task.
  3. Complete the requested identity, package or signing-key ownership step; use the certificate that signs the distributed artifact.
  4. After the console reports completion, query the same package and certificate pair again and save the result with the release record.

Quick facts

RegistrationNot recognized
First checkProduction package name
AvoidUnplanned key rotation
Field note

A NOT_REGISTERED response is an API result, not a failed HTTP request. Do not create a replacement package or rotate a key just to change it; package identity affects updates, links, permissions and user continuity. For Play apps, inspect the account's Play Console Home task as well as the API result.

Detailed guidance

Treat NOT_REGISTERED as a result to remediate

For a package-only request, NOT_REGISTERED means the package name is not linked to a verified developer in the status service. With a certificate supplied, it means the queried package-and-certificate pair is not registered. HTTP 200 with this state is a successful API response, not a network failure.

Confirm the final production application ID for the affected store artifact, then open the Play Console or Android Developer Console account that distributes it. Complete the package or ownership step shown there. Do not create a replacement package or rotate a signing key to change the status.

  • Check the package from the production variant, including its flavor suffix.
  • Use the console for the distribution path and account owner.
  • If a signed APK challenge appears, verify the selected key and follow that exact workflow.
  • Recheck the same package-and-certificate pair after the console reports completion.
Illustrative HTTP 200 response body; not a live query
{
  "name": "packages/com.example.app/packageRegistrationStatus",
  "state": "NOT_REGISTERED"
}

Have the production package name and signing certificate ready? Query the official registration state, then use the result to choose your next step.

Run status check →

Frequently asked questions

Does NOT_REGISTERED mean someone else owns the name?

No. The status only says the queried package or package-and-certificate pair is not registered in the official service. Confirm the input and account, then check the console for package eligibility or a pending ownership step. Do not interpret this state as proof that another developer owns the package name.

Should CI retry this state automatically?

No. A 200 response with NOT_REGISTERED is a stable registration state that needs console remediation, unlike a transient 429, 500 or 503 error. Retry only after the console reports the requested action complete, using the same production package and certificate inputs.

Sources and review

Last reviewed: