Ownership proof

adi-registration.properties Android verification guide

For an existing package-name ownership challenge, the console provides an account-specific snippet. Put that exact snippet in an asset named adi-registration.properties, build a release APK with the matching private signing key, then upload the APK in the same registration workflow.

Guide summary

Place adi-registration.properties in an Android APK correctly when Play Console or Android Developer Console asks you to prove signing-key ownership.

For: Developers proving ownership of an existing Android package name with a signed APK.

Release sequence

  1. Copy the snippet from the active package-registration challenge in the official console.
  2. Create app/src/main/assets/adi-registration.properties with the exact filename and snippet.
  3. Build a release APK signed by the private key matching the selected public SHA-256 fingerprint.
  4. Inspect the APK asset and certificate, then upload it to the same console challenge.

Quick facts

Native asset pathapp/src/main/assets/
ArtifactSigned release APK
ProofSnippet plus matching signing key
Field note

The console-generated snippet is not a private signing key. Do not substitute a guessed value, rename the file with a .txt suffix or sign the proof APK with an upload key that does not match the selected certificate.

Detailed guidance

Verify the APK before upload

The ownership challenge is bound to the console flow and the selected public certificate. The asset proves that the APK was prepared for this challenge; the APK signature proves control of the matching private key.

After building, confirm the asset exists at assets/adi-registration.properties inside the APK and run apksigner to verify the certificate. If the console rejects the artifact, check filename, path, snippet, package name and signing certificate before rebuilding.

  • Use the exact snippet from the active console challenge.
  • Keep the .properties extension with no added .txt.
  • Sign with the private key matching the selected SHA-256 certificate.
Inspect the APK
unzip -l app-release.apk | grep 'assets/adi-registration.properties'
apksigner verify --print-certs app-release.apk

Frequently asked questions

Is the snippet my private signing key?

No. The private key remains in your keystore or signing service. The console snippet is placed in the APK asset for the ownership challenge.

Can I use an empty project?

Official console guidance permits an empty project with the same package name for the proof APK, provided the required asset and matching signing key are used.

Sources and review

Last reviewed: