Home / Core workflow
Core workflow

How to check Android app registration status

Check whether an Android package is registered and whether its production signing certificate matches Google's registration record.

Operational summary

A package-only check answers whether a package name is registered to a verified developer. Adding a certificate fingerprint distinguishes a correct registration from a package registered with another signing identity.

Built for: Release engineers and developers who need an auditable preflight check before shipping or migrating an Android app.
Package-only resultRegistered or not registered
Package + certificateAlso detects a fingerprint mismatch
Data sourceAndroid Developer ID Status API

Recommended sequence

  1. Enter the fully qualified package name, such as com.example.app.
  2. Add the 64-character SHA-256 signing certificate fingerprint when available.
  3. Run the check and save the recommended next action, not the API key or signing material.
  4. Confirm the final state in Play Console or Android Developer Console.
Field note: This site proxies the official status request. It never asks for a private signing key; only a public certificate fingerprint is used.

Run two checks when the certificate matters

A package-only request answers whether any verified developer has registered the name. It does not prove that your release certificate is the credential on file. Follow it with the production SHA-256 fingerprint when you control or can inspect the distributed artifact.

Record the exact input and checked time alongside the release. If the package is registered but the fingerprint differs, investigate Play App Signing, legacy keys and channel builds before taking corrective action.

  • REGISTERED: continue with store and release checks.
  • NOT_REGISTERED: verify the package value, then complete registration.
  • REGISTERED_WITH_ANOTHER_CERTIFICATE_FINGERPRINT: trace signing history.

Frequently asked questions

Can I check with only a package name?

Yes, but that only confirms the name is registered. Add the production certificate fingerprint to validate the signing identity.

Does PkgReady upload my APK?

No. It accepts a package name and an optional public SHA-256 fingerprint; it never needs the APK or private key.

Sources and review

PkgReady summarizes operational implications but does not replace an official console or Android documentation. Reviewed 2026-08-14.