Google Play Closed Testing for Unity Games
Done in 6 Hours

Why Unity Developers Get Stuck on Closed Testing

You spent months building your game in Unity. You exported the APK or AAB, set up Google Play Console, and then hit the wall that stops thousands of indie game developers: Google requires 12 real testers active for 14 consecutive days before production access.

Unity game developers face extra challenges recruiting testers:

• Game testers are harder to keep engaged for 14 full days than app testers
• Large APK sizes from Unity builds mean some devices have download issues
• Testers need to actively open the app periodically, not just install and ignore it
• Finding 12 people willing to test a game they did not ask for takes weeks
• Every failed attempt resets your 14-day clock to zero

How TestLaunch Pro Works for Unity Games

1. Purchase your package — choose 12 or 25 testers. Checkout takes 2 minutes via Stripe.
2. Set up your closed testing track — we send you exact step-by-step instructions for the Google Play Console, including Unity-specific build requirements.
3. Send us your invite link — we deploy your testers. All 12 opt in using the correct Google account required by Play Store.
4. Testers stay active for 14 days — we manage engagement reminders so testers remain active. Your 14-day clock runs uninterrupted.
5. Apply for production access — once 14 days are done, submit your application. Your Unity game goes live on Google Play.

Unity Build Requirements for Google Play

Build your release APK or AAB

In Unity, go to File - Build Settings - Android. Enable IL2CPP scripting backend and ARM64 target architecture. Build as an AAB file (required by Google Play since 2021) and upload it to your closed testing track.

Keystore signing

Unity builds require a keystore to sign your release build. Set this up in Player Settings - Publishing Settings before building. Once uploaded to Play Console, enable Google Play App Signing to protect your key.

Target API level

Google Play requires apps to target API level 34 (Android 14) or higher for new submissions. Set this in Player Settings - Other Settings - Target API Level. Our tester pool covers Android 8.0 and above.

Content rating

Complete the content rating questionnaire in Play Console before adding testers. Without a rating, the app may not be visible to testers in some regions.

Frequently Asked Questions

Does this work with any Unity game genre?

Yes. Puzzle games, action games, RPGs, hyper-casual games — any Unity-built game that is uploaded to the closed testing track in Google Play Console qualifies. We do not test the gameplay ourselves; testers simply need to have the app installed and active.

My Unity APK is very large. Will that cause problems?

We recommend using an AAB instead of APK for large games, as Google Play delivers the right assets for each device, reducing download size. If your game is over 150MB as an APK, switching to AAB often cuts the install size significantly.

Do testers need to play the game or just install it?

Google Play's requirement is that 12 testers have the app installed and active on their devices for 14 consecutive days. Testers do not need to play or review the game. Our testers keep the app installed and active for the full 14-day period.

What if my Unity game gets a policy violation?

Our service solves the closed testing requirement only. If Google flags your game for a policy issue unrelated to testers, our 30-day money-back guarantee still applies. We will refund you in full.