Ownership proof

adi-registration.properties: APK location and signing-key verification

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

Find where adi-registration.properties belongs in your APK, complete the signing-key ownership challenge, and troubleshoot verification failures.

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

Build and verify the ownership-proof APK

The console creates the account-specific snippet when it asks you to prove control of an existing package and signing key. Save it exactly as app/src/main/assets/adi-registration.properties, then build the release APK with the private key whose public SHA-256 certificate you selected. The properties file is evidence for this challenge; it is not a private key.

Before upload, read the file directly from the APK and inspect the signing certificate. If verification fails, check the active challenge snippet, exact filename, assets path, applicationId and certificate before rebuilding.

  • Use the exact snippet from the active console challenge.
  • Keep the .properties extension with no added .txt.
  • Upload the signed APK back to the same console workflow.
Inspect contents and certificate
unzip -p app-release.apk 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: