Identity input

Find an Android package name without guessing

The registration API needs the exact, fully qualified package name. A display name such as “My Notes” is not enough, and a debug application ID may differ from production.

Guide summary

Locate the exact Android application ID or package name in Gradle, an installed app, Play Console or an APK before checking registration.

For: Developers, QA teams and app portfolio owners collecting package identifiers across multiple projects.

Release sequence

  1. Check applicationId in the app module's Gradle configuration.
  2. For variant-aware builds, include applicationIdSuffix values before testing.
  3. Cross-check the package shown in the Play Console app URL or release metadata.
  4. Use the production ID, not a debug or internal-test suffix.

Quick facts

Expected formatcom.company.product
Case sensitivityPreserve the source value
Common mistakeChecking a debug application ID
Field note

The namespace used for generated code and the final applicationId can differ. Registration follows the installed package identity.

Detailed guidance

Read it from the Android project

The app module's applicationId is the installed package identity. namespace controls generated code and may be different. Resolve product flavors and applicationIdSuffix for the exact release variant before copying the value.

Gradle example
android {
  namespace = "com.example.code"
  defaultConfig { applicationId = "com.example.app" }
}

Read it from a built APK

Inspect the artifact you intend to distribute when source and CI configuration are unclear. The command prints a value such as com.example.app; it does not return the marketing name shown beneath the launcher icon.

APK command
apkanalyzer manifest application-id app-release.apk
# com.example.app

Read it from an installed app or store listing

With a device connected, query packages and filter by a distinctive part of the ID. In Google Play URLs, the id query parameter is the package name. Cross-check either value against the production release record.

  • Do not use the app's display name.
  • Do not drop a production flavor suffix.
  • Use the identity from the distributed release, not a debug build.
Device and Play examples
adb shell pm list packages | grep example
https://play.google.com/store/apps/details?id=com.example.app

Check the package after you find it

Run a package-only registration check first. Add the production certificate SHA-256 when you need to prove that the registered signing identity matches the artifact users receive.

Frequently asked questions

Is namespace always the package name?

No. Modern Android projects can use namespace for generated code while applicationId defines the installed package.

Can two variants have different registration states?

Yes. If variants install under different application IDs, each package name is a separate registration identity.

Sources and review

Last reviewed: