Do Closed Testers Have to Pay for a Paid App?
Testers must buy a paid app in a closed test, and the price applies to every track at once. What license testing removes from the bill, and what it leaves.
Read the articleHow the Play testing tracks work, where testers come from, and what shows up in a campaign that has to survive a review.
Testers must buy a paid app in a closed test, and the price applies to every track at once. What license testing removes from the bill, and what it leaves.
Read the articleOnly some testers got the build. Google picks rollout recipients at random and tells nobody, and a first release cannot be staged at all. What to check first.
No rename, ever. Google has one narrow deletion path that frees a package name, and the install count decides it. What a change costs your closed test.
Internal app sharing moves a build in minutes and counts for nothing. Its 100-download and 60-day limits, plus the re-signing trap that breaks sign-in.
A restricted permission can hold your test release in pending publication for weeks, before the 14-day clock starts. What to strip, what to declare.
Tester sign-in fails because the OAuth client is pinned to a different certificate than Play delivers. The two lists and one publish step that fix it.
FlutterFlow's first closed-test upload lands as a draft, so the 14 days never start. The exact rollout step, AAB limits, and the 12-tester gate.
Play Console checks your changes before Google reviews them. What a critical check blocks, what Proceed anyway does, and why the 14 days can't start yet.
Google allows several closed tracks at once but writes the 12-tester rule about one test. Where opt-in attaches, why 6 + 6 is not 12, and five traps.
Closed testing apps are not in Play search, and testers cannot leave public reviews. What Google documents, what non-testers see, and five traps.
Watch and TV builds still need 12 opted-in testers for 14 days. Why device ownership blocks installs, what Google counts, and the review that follows.
A tester opens your opt-in link and Play says the device isn't compatible. The four filters behind that message, how to confirm which fired, and the fix.
v0 ships a Vercel web app, not an Android build. Wrap it with Capacitor, build the AAB, and clear the 12-tester closed test — the full Play Console path.
Personal library apps need no developer account and no 12 testers. What Google does when you graduate to publish — and when your 14-day clock starts.
Sign-in works on your phone but fails for every tester? Google re-signs your bundle: register the app signing key fingerprint, not the upload key's.
Rork builds and signs your Android AAB, but Play Console stays manual. What Rork's docs skip, and the internal-testing trap that delays your 12-tester count.
Installed audience vs DAU in Play Console: what each closed-testing number means, why the charts lag or come up blank, and what Google actually checks.
Base44 generates a Play-ready AAB from its Mobile app tab, but the package name is fixed, Billing is missing, and 12 testers still apply.
Replit's Agent now builds the signed .aab for you, but Play Console stays manual. What Replit's docs skip, and how to clear the 12-tester closed test.
Play Console keeps Pre-registration locked until your closed test meets the 12-tester rule. Why it's disabled, the 90-day limit, and how testing interacts.
Email list or Google Group? Both count the same toward Google's 12-tester rule. Google's exact limits, the join-order trap, and which to pick (Oct 2026).
AI Studio only publishes to Google Play's internal testing track. Complete app setup, open a closed test, then run the 12-tester, 14-day clock.
Bolt hands you a web URL or an Expo project, never an app bundle. Build the .aab, skip internal testing, then run the 14-day closed test with 12 testers.
Production access under review? Play Console shows three different kinds of status. See what each one means, which one is your application, and what to do next.
Google says production access review takes seven days or less, but can occasionally take longer. What it promises, what developers report, and what to check.
Why the Apply for production button is missing or greyed out: it lives on the Dashboard, not the Production page. Seven causes, checked in order.
New personal Play Console accounts must verify a real Android device before publishing. See the exact steps, device rules and what it means for your closed test.
Google needs working test credentials to review a login-gated app. Where App access sits in Play Console, what Google requires, and how to fix a rejection.
Lovable publishes a web app, not an Android bundle. Wrap it, sign the .aab, run the 14-day closed test with 12 testers, then apply for production access.
Android developer verification went live on 30 Sep 2026. Can it block your 12-tester closed test? Check registration and fix a tester who cannot install.
An uninstall does not opt a tester out — and Google never says what it does to your count. What the docs state, how to spot it, and the fix that works today.
Do testers need to open the app every day? Google publishes no daily-open rule for closed testing. What its docs actually require, and how often to ask testers.
Every question on Google's production access form, what the reviewer checks in each answer, and a worked example per field. Checked against Google's docs.
Paid Google Play tester services run $14.99 to $31.23 per app in 2026. What Google actually publishes about paying testers, and when you should not pay.
Google's email says your app requires more testing. The two reasons it names, under 12 opted-in testers or insufficient engagement, and how to fix each.
Play Console gives you no delete for a closed testing track. Google's fix is Pause track — plus four other official removals for what you actually want gone.
Added 20 emails and Play Console still says 0 testers currently opted in? The counter only moves on completed opt-ins. Seven causes, checked in order.
Google's help page never mentions a global timer. What it says about continuous opt-in, why four guides disagree, and what to do at 11 testers.
Cross-platform release builds behave differently from the debug build in your editor. What to check before a Flutter or React Native app enters closed testing.
Register, create the app and choose your tester count. Every plan includes the same monitoring, support and participation guarantee.