Find 12 Testers for WearOS Apps & Watch Faces (2026 Guide)

Android Studio users:

Go to Build → Generate Signed Bundle/APK and note the keystore path. Common locations include your project folder or ~/.android/

Galaxy Watch Face Studio users:

Go to Project → Build → Manage Certificates to export your keystore. Select your certificate and click Export to save the .jks file.

This error occurs when the version code in your AAB is lower than or equal to a previously uploaded version.

Solution: Check your current version code in Play Console under Release → App Bundle Explorer. Then regenerate your companion app with a higher version code.

If you're enrolled in Play App Signing, you can request an upload key reset through Google Play Console. This allows you to create a new keystore while keeping your existing app listing.

If you're not enrolled and have lost your keystore, unfortunately you cannot update your existing app. You would need to create a new app listing with a new package name.

Yes. You can sign AAB files using multiple methods:

• Android Studio - Build → Generate Signed Bundle
• jarsigner - Command-line tool included with Java JDK
• apksigner - Part of Android SDK build tools

Use the AI prompt provided earlier in this guide for step-by-step instructions.

• Generate companion app: 5-7 minutes
• Sign the AAB: 2-5 minutes
• Google review: 1-3 days
• Closed testing period: 14 days minimum

Yes, the signing tool is completely safe. It is fully open source, so you can inspect every line of code yourself to verify exactly what it does:

• The entire source code is publicly available, you can check the code of the signer directly
• Files are processed server-side and deleted immediately after signing
• Uses the official Java jarsigner tool under the hood
• Your keystore credentials are never stored, logged, or transmitted anywhere
• No data is retained after your signing session ends

Being open source means full transparency, there are no hidden processes or data collection. If you still prefer to sign locally, you can use the AI prompt provided earlier in this guide.

Google introduced the 12-tester requirement in 2023 to combat spam and low-quality apps on the Play Store. By requiring developers to have real users test their app for 14 days, Google ensures:

• The app has been validated by real users before public release
• Developers are committed to their app's quality
• Spam and malicious apps are filtered out early

Google Play closed testing is a pre-release testing track that allows you to distribute your app to a limited group of testers before making it publicly available. Key features:

• Only invited testers can access and download the app
• Testers must opt in via a testing link you provide
• The app is not visible on the public Play Store during testing
• You need at least 12 testers who have opted in
• Testing must run for a minimum of 14 consecutive days

To get production access for your WearOS app or watch face:

• Complete the 14-day closed testing period with 12+ active testers
• Fill out all required store listing information
• Complete the content rating questionnaire
• Submit the data safety form
• Request production access in Play Console

Using the companion app strategy, your phone app testers count toward the WearOS app requirements.

No. That's the beauty of the companion app strategy:

• Testers only need a regular Android phone
• They install and test the companion app on their phone
• These testers count toward your WearOS app's 12-tester requirement
• No Galaxy Watch, Pixel Watch, or other WearOS device is needed

This makes finding testers significantly easier since Android phone users are far more common than smartwatch owners.

After completing the 14-day closed testing period with at least 12 testers:

• You become eligible to apply for production access
• Go to Play Console → Release → Production → Create new release
• Google will review your production release request
• Review typically takes 1-7 days depending on app complexity
• Once approved, your WearOS app or watch face goes live on the Play Store

Yes, the same testers can help test multiple apps. However, each app requires its own:

• Separate closed testing track
• Unique testing opt-in link
• 14-day testing period (periods can run simultaneously)
• Companion app with matching package name

If you have multiple watch faces to publish, you'll need to create a companion app for each one with the corresponding package name and keystore.

Finding testers for WearOS apps and watch faces can be challenging since you'd normally need people with smartwatches. Here are the best approaches:

• Use the companion app strategy - As described in this guide, create a companion phone app so regular Android phone users can count as your testers. No smartwatch needed.
• WearOS communities - Share your testing link in WearOS and Galaxy Watch forums, Reddit communities (r/WearOS, r/GalaxyWatch), and Discord servers.
• Social media - Post in watch face and WearOS groups on Facebook, X, or other platforms where enthusiasts gather.
• Professional testing service - Use a service like Testers Community to get verified testers who will actively test your app throughout the full 14-day period.

The companion app approach is by far the easiest, it removes the smartwatch barrier entirely and lets any Android phone user help you meet Google's 12-tester requirement.