# Play Store App Ownership Verification > Prove you own the website your app wraps, which Play now asks for. - **Applies to:** AppMint and Appwright - **Source:** the Integration Guide shipped inside the app; this page is generated from it. - **HTML:** https://freewebtoapk.com/docs/play-store-ownership-verification Prove APK Ownership to Google Without a PC ### 1. What Is Play Store App Ownership Verification? Google Play has a challenge-response system that lets you prove you are the legitimate owner of an APK without needing Android Studio or a PC. When does this happen? - A user or business partner asks you to prove the APK they have is yours - Google Play or a distributor sends you a verification token - You need to inject that token into the APK and re-sign it The token is a small text file (adi-registration.properties) placed inside the APK's assets folder. Google then downloads and installs the APK to confirm the token matches their records. ### 2. Open the Play Store Verification Tool _(AppMint only)_ The verification tool is built directly into the WebToApk Generator app: 1. Open the generator 2. Tap the ☰ menu (top-left) 3. Tap '🛡️ Play Store Verification' No PC, Android Studio, or command-line tools needed. ### 2. Open the Play Store Verification Tool _(Appwright only)_ The verification tool is built directly into Appwright: 1. Open the generator 2. Tap the ☰ menu (top-left) 3. Tap '🛡️ Play Store Verification' No PC, Android Studio, or command-line tools needed. ### 3. Step 1 - Pick Your APK File _(AppMint only)_ Tap 'Pick APK File' and select the generated APK you want to verify. ✅ This should be the same APK you submitted to (or generated for) Google Play. ⚠️ The APK must have been generated by this app so the signing key is available. APKs signed with external keys cannot be re-signed here. ``` APK file location after generation: Downloads/WebToApk// Example: Downloads/WebToApk/MyShopApp/MyShopApp.apk ``` ### 3. Step 1 - Pick Your APK File _(Appwright only)_ Tap 'Pick APK File' and select the generated APK you want to verify. ✅ This should be the same APK you submitted to (or generated for) Google Play. ⚠️ The APK must have been generated by this app so the signing key is available. APKs signed with external keys cannot be re-signed here. ``` APK file location after generation: Downloads/_v_.apk Example: Downloads/MyShopApp_v1.0_20260831_142530.apk ``` ### 4. Step 2 - Paste Your Verification Token Google (or whoever requested verification) will send you a token string. It typically looks like a random alphanumeric code. Paste it into the 'Verification Token' field exactly as received - do not add spaces or line breaks. ``` Example token format: adi-registration.properties content: token=eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9... (Paste ONLY the token value, not the key name) ``` ### 5. Step 3 - Generate & Sign Verified APK _(AppMint only)_ Tap 'Generate Verified APK'. The tool will: 1. Read your original APK 2. Remove any old META-INF verification files 3. Inject assets/adi-registration.properties with your token 4. Re-sign the APK with your app's original signing key 5. Save the verified APK to your Downloads folder The entire process runs on-device in seconds. ``` Output file: Downloads/WebToApk/Verified/_verified.apk ``` ### 5. Step 3 - Generate & Sign Verified APK _(Appwright only)_ Tap 'Generate Verified APK'. The tool will: 1. Read your original APK 2. Remove any old META-INF verification files 3. Inject assets/adi-registration.properties with your token 4. Re-sign the APK with your app's original signing key 5. Hand you the finished APK, ready to share (Step 4) The entire process runs on-device in seconds. ``` The verified APK stays inside Appwright until you send it. Step 4’s 'Share APK' hands it straight to email, Drive or chat — it is never written to your Downloads folder. ``` ### 6. Step 4 - Share the Verified APK After generation, tap 'Share APK' to send it directly to: - Email (attach to your reply to Google) - Google Drive / OneDrive - WhatsApp / Telegram - Any other sharing method Send the verified APK back to whoever requested the verification. Google's system will automatically download it, extract the token, and complete the ownership check. ### 7. What Gets Injected Into the APK? The tool injects a single properties file at the path required by Google: ``` File path inside APK: assets/adi-registration.properties File content: ``` ### 8. Signing Key Details The verified APK is re-signed using the same deterministic key that was used when the original APK was generated. The key is derived from your app's package name, so: ✅ The verified APK has the exact same signature as your submitted APK ✅ Google can confirm the signer matches their records ✅ No keystore file needed - the key is computed automatically ⚠️ Important: This only works for APKs generated by this app. It cannot re-sign APKs from other tools. ### 9. Frequently Asked Questions Q: Will this break my app or change its behavior? A: No. The only change is the addition of the properties file in assets. All other functionality stays identical. Q: Do I need to update my Play Store listing? A: No. The verified APK is used only for the ownership challenge, not submitted as a new release. Q: Can I verify multiple APKs with different tokens? A: Yes - run the tool once per APK/token combination. Q: My token expired. What do I do? A: Contact Google to request a new token, then repeat this process with the fresh token.