To complete verification for an existing package name, you must sign and upload an APK using the private key corresponding to the public key that you provided.
- Select Upload APK to open the ownership verification user journey.
- The next screen will show the package name, the selected SHA-256 public certificate and signing guidance.
- Copy your snippet – a unique identifier tied to your developer account.
- Prepare the APK: In your IDE (using an empty project with the same package name or your actual app), navigate to your app's source tree.
- Inside the assets folder, create a file named exactly
adi-registration.properties. - Open the file and paste the snippet.
- Review the sample project on GitHub to confirm the correct structure and snippet placement for proof of ownership.
- Build and sign: Build a release APK and sign it with the private key that corresponds to the public certificate fingerprint. The signature (via
jarsigneror Gradle'ssigningConfigs) serves as proof of legitimate ownership.
Note: Package name registration for apps with delegated signing keys
If the package name that you are registering belongs to an app where the private signing key has been delegated to a third-party distribution platform, like the Samsung Galaxy Store, you must follow these steps instead when proving ownership of the private key.
- Build and upload your release APK or AAB to the distribution platform.
- Download the final signed release APK directly from that distribution platform.
- Upload the signed APK that you downloaded to Play Console in 8.
- Upload: Return to Play Console, select Upload, locate your signed release APK and upload it. Android will check the signature and register your ownership.
Get help
Contact us for more help with Android developer verification in Play Console.