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

Resolve the final application ID

In Android builds, namespace and applicationId can be different values. Product flavors and applicationIdSuffix can also change the installed identity. Read the final release variant rather than copying the first package-like string you see in source code.

For an APK, use Android build tools such as aapt2 dump badging or apkanalyzer manifest application-id. Cross-check that result against the store listing and your release metadata.

  • Do not use the marketing display name.
  • Do not omit a release flavor suffix.
  • Preserve dots, underscores and letter case from the source value.
APK example
apkanalyzer manifest application-id app-release.apk

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: