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 facing an unresolved package before a regional enforcement milestone.

Release sequence

  1. Recheck the exact production application ID and remove accidental debug suffixes.
  2. Verify that the intended developer account owns the registration workflow.
  3. Complete or repair package registration in the appropriate official console.
  4. Allow for propagation, then run the same package and certificate check again.

Quick facts

RegistrationNot recognized
First checkProduction package name
AvoidUnplanned key rotation
Field note

Do not create a new package merely to get a different result. Package identity affects updates, links, permissions and user continuity.

Detailed guidance

Triage the input before the account

First confirm the final production application ID. Debug suffixes, product flavors and copied display names are common causes of false investigations. Then determine whether the package should be managed in Play Console or Android Developer Console.

If registration was just completed, retain the exact input and retry after the console reports completion. Do not generate a replacement package name or rotate a signing key simply to change the status.

  • Validate the package name.
  • Confirm the correct developer account.
  • Complete ownership proof and wait for the official status.
Representative response
{
  "state": "NOT_REGISTERED"
}

Frequently asked questions

Does NOT_REGISTERED mean someone else owns the name?

Not necessarily. It can also mean the package has not completed registration or the queried identity is wrong.

Should CI retry this state automatically?

No. It is a stable business state that needs investigation, unlike a transient 500 or 503 response.

Sources and review

Last reviewed: