Prerequisites
Before you begin, make sure you have:
- Your keystore file — The same
.jksfile you used to sign your watch face or WearOS app - Keystore credentials — Password, key alias, and key password
Critical: Use the same keystore
The companion app must be signed with the exact same keystore you used for your watch face or WearOS app. Using a different keystore will result in a signature mismatch and Google Play will reject the upload.
Step 1
Generate the Companion App
Use our free Companion App Generator to create a phone app that matches your watch face or WearOS app. The tool builds a simple companion app that displays your watch face preview and includes basic settings.
Enter your app name — Use the same name as your watch face for consistency
Enter your package name — This must exactly match your watch face's package name
Upload a preview image — A screenshot or preview of your watch face (400x400px recommended)
Fill optional fields — Privacy policy URL, support email, and version details
Click Generate — Wait 5-7 minutes while the app is built
Download files — Get the AAB file (for Play Store) and optionally the APK (for testing)
Package name must match exactly
Double-check your watch face's package name before generating. Even a small typo will prevent the apps from being linked on Google Play.
Step 2
Sign the AAB File
The AAB file you downloaded is unsigned. Before uploading to Google Play, you need to sign it with your keystore. The easiest way is to use our free online signing tool.
Security & Privacy
The signing tool is open source and processes files server-side using the official Java jarsigner. Your keystore and credentials are never stored — files are deleted immediately after signing.
Alternative: If you prefer to sign locally on your own machine, you can use the prompt below to get step-by-step guidance.
Prefer to sign locally with AI guidance?
Copy this prompt and paste it into ChatGPT or Gemini. Replace the placeholders with your details, and it will guide you through signing on your own machine.
I have an unsigned AAB file for a WearOS companion app and a keystore file (.jks). **My Setup:** - Operating System: [REPLACE: Windows / macOS / Linux] - Keystore file location: [REPLACE: path to your .jks file] - Unsigned AAB location: [REPLACE: path to companion-app.aab] **Important:** This companion app must be signed with the SAME keystore I used for my WearOS watch app. Please guide me step-by-step on how to: 1. Verify my keystore is valid and check the alias name 2. Sign the AAB file using jarsigner with SHA256withRSA 3. Verify the signature was applied correctly Include the exact commands I need to run for my operating system.
Step 3
Upload to Google Play Console
With your signed AAB ready, head to the Google Play Console to upload your companion app.
Create a new app in Google Play Console (or use your existing watch face listing)
Go to Closed Testing and create a new track if you don't have one
Upload the signed AAB — Google will verify the signature matches your app
Complete the store listing — Add description, screenshots, content rating, and data safety form
Add testers and start testing — Invite 12+ testers to join your closed testing track
After 14 days of successful testing
Once your companion app passes the 14-day closed testing requirement with 12+ testers, you can promote your watch face directly to production. The testing requirement is shared across both form factors!
🎉 That's it! You've completed all the steps.
Now you just need 12 testers to join your closed testing track and actively test your app for 14 days. Once that's done, your watch face will be eligible for production release on Google Play.
Need Help Finding Testers?
Don't have 12 testers? Our professional testing service provides verified testers who will actively test your companion app throughout the 14-day period.