Android Developer Verification — Package Name Registration
How to register an Android package name for developer verification: provide the package
details, register your signing key, prove ownership by uploading a signed APK containing the
adi-registration.properties file, and track the result.
The process differs slightly depending on whether your package name is new (never seen on
Android) or existing (already has installs). This guide covers both.
Prerequisites
Before starting the deployment process,
ensure you have:
- The release signing key and keystore credentials (store password, key alias, key
password)
- JDK installed (keytool is included)
- Google Play Console access with identity verification already completed
- Your app's SHA-256 certificate fingerprint (how to obtain it)
Step 1: Provide package name details
Common to both new and existing package names.
- Open Google Play Console and go to the Android developer verification page.
- On the Package names tab, select Register package name.
- Enter the package name you want to register.
- Provide a friendly name for easy identification within Play Console.
- Select Next to proceed.
Step 2: Register Your Signing Key
The next step depends on whether
your package name is new or already existing on Android.
A. New Package Name
For package names that have never been used on Android,
you only need to provide the public certificate
from your signing key.
- Select Add key
- Provide the public key certificate
- Paste or upload your signing certificate
- Click Add key to continue
B. Existing Package Name
For applications that already have installs on Android,
you must select an eligible signing key fingerprint.
- Select Select key
- View the list of eligible certificate fingerprints
- Search or scan for your certificate fingerprint
- Select the correct signing key
- Click Add key
Important:
Eligibility follows Google's package-sharing rules
such as majority key holder verification,
50+ installs requirement,
or first-come-first-served policy.
If your certificate fingerprint is not listed
as eligible:
- Expand the Other Keys list
- Request permission to use the package name
- Provide a proper rationale to Google
- Wait for Google's verification review
Google may reject the request
if ownership or eligibility requirements are not satisfied.
Step 3: Prove Private Key Ownership (Existing Packages)
Existing package names require a signed APK
as proof of private key ownership.
Important:
The APK must be signed using the private key
that matches the registered signing certificate.
3.1 Copy the Snippet
- Select Upload APK
- Open the ownership verification flow
- Review the displayed package information
- Copy the generated verification snippet
The verification screen displays:
- Package name
- Selected SHA-256 certificate
- Signing guidance
- Unique verification snippet
Note:
The snippet is uniquely tied
to your Google Play developer account.
3.2 Create adi-registration.properties File
Create the following file
inside your Flutter project:
android/app/src/main/assets/adi-registration.properties
- Create the
assets folder if it does not exist
- Filename must be exactly
adi-registration.properties
- Do not add a
.txt extension
- Paste the copied verification snippet into the file
- Save the file
Warning:
The file path must be exact.
If the file is placed in the wrong location,
ownership verification will fail.
3.3 Build & Sign the Release APK
Build the signed release APK
using your registered signing key.
Generated APK Location
build/app/outputs/flutter-apk
The APK must be signed using:
- Gradle
signingConfigs
- Or
jarsigner
Note:
The APK signature acts as proof
of ownership for the package name.
Delegated Signing Keys
If your signing key is managed
by a third-party platform
(for example Samsung Galaxy Store):
- Upload APK/AAB to the third-party platform
- Download the final signed APK
- Use the downloaded APK for verification upload
3.4 Upload APK to Play Console
- Return to the verification screen
- Select Upload
- Select the signed release APK
- Upload the APK file
Google Play will:
- Verify the APK signature
- Validate file contents
- Confirm ownership verification
Step 4: Track the Registration
After completing verification,
Google Play formally registers the package name
and links it to your verified developer identity.
- You will receive an email confirmation after successful registration
- Monitor registration and signing key status from the Android Developer Verification page
Troubleshooting
| Issue |
Cause |
Fix |
| File not found |
File placed in project root
instead of assets folder
|
Move the file to:
android/app/src/main/assets/
|
| Signature mismatch |
APK signed with wrong or debug key
|
Sign the APK using the private key
matching the registered certificate
|
| Wrong filename |
File saved with .txt extension
|
Rename the file exactly to:
adi-registration.properties
|
| Key not eligible |
Certificate fingerprint not listed
|
Expand other keys and submit
a verification request with rationale
|
Note:
For Expo or managed workflow projects,
the default JavaScript bundler
does not automatically copy files
into the native Android assets folder.
Use a config plugin or prebuild process
to ensure the file is copied into:
android/app/src/main/assets/
inside the final APK build.
Need Help?
Feel free to contact our support team for any issues, questions, or
guidance.
Support Policy
Scope of Support
- Installation assistance
- Bug fixing & issue resolution
- Basic guidance on features
Not Included:
- Custom feature development
- Code modifications or customization
- Server configuration or hosting issues
- Third-party integrations or services
Support
Your feedback helps us improve XpressHive.
If you have suggestions, feature requests, or ideas, feel free to share them with
us.
