Google Play 14-Day Closed Testing Checklist

Understanding the 14-day requirement

Google Play requires that your closed testing track has at least 12 opted-in testers who remain active for 14 consecutive days before you can apply for production access. This applies to personal developer accounts that have not previously published an app on the Play Store.

The 14 days must be continuous. If testers become inactive or your opt-in count drops below 12 during the window, the clock may be affected and your production access application reviewed more strictly.

Before day one

Confirm your Play Console closed testing track is active and the invitation link is working

Verify that your closed testing link reaches real Android users, not just email addresses

Prepare your app package name and SHA-256 APK fingerprint for DevSwap room submission

Set up or join a DevSwap testing room with at least 12 confirmed members

Identify which apps you are responsible for testing in return

Days one to three

Focus on confirming that all 12 testers have successfully opted in and that their devices show up in your Play Console closed testing dashboard. An opt-in in DevSwap does not automatically mean a Play Console opt-in — both need to happen.

Use DevSwap room activity signals to identify any testers who installed but have not yet opened the app. The first 72 hours are the easiest time to address gaps before they become a pattern.

Days four to seven

By this point, every tester should have at least one confirmed session. Monitor your room health score daily. Check which members have completed their assigned testing for other apps in the room, since mutual participation drives accountability across the whole group.

If a member has missed participation for two or more consecutive days, reach out directly or flag the room to begin finding a replacement.

Days eight to fourteen

The second week is where many closed testing cycles fail. Testers who were active in week one may slow down. DevSwap daily participation indicators make it possible to see who is trending toward inactivity before the damage is done.

Keep participating in other developers apps to maintain room cohesion. Active rooms tend to stay active because mutual obligation keeps everyone engaged through the full window.

After the test

Review all feedback collected during the testing period and prioritise any critical issues

Confirm that your Play Console shows continuous tester activity for the full 14 days

Prepare your production access request with complete testing evidence

Export your tester participation log from DevSwap if you need to document the testing cycle

Using integrity signals throughout

Package names, SHA-256 fingerprints, Guard monitoring, and room logs make the testing cycle easier to manage and verify. SHA-256 verification confirms that testers installed the real app, not a modified or cloned version. Guard session data shows genuine engagement beyond a single install.

These signals give you confidence that your production access request is supported by real, verifiable testing activity rather than just a set of opt-in email addresses.