How long does Google Play production access review take?

Updated

The short answer comes from Google: once you apply for production access, review usually takes seven days or less, but can occasionally take longer, and the result is emailed to the account owner. That quote is from Google's app testing requirements page, and it is the only official number there is. We have not replaced it with an average of our own, because nobody outside Google has one worth trusting.

The more useful answer is the whole timeline, because the review is only one of five waits, and it is rarely the longest.

The full timeline, closed test to live app

StageHow longWho controls it
1. Closed-track release reviewed and publishedHours to days; the opt-in link can take several hours after publishingGoogle, then you
2. Recruiting twelve testersAnywhere from a day to weeksYou
3. Twelve testers opted in continuouslyAt least 14 days, fixedThe rule
4. Production access application reviewUsually seven days or less, per GoogleGoogle
5. First production release reviewVaries; a separate reviewGoogle

Two things fall out of that table. First, stage 3 cannot be shortened, so the realistic minimum from your twelfth opt-in to a public app is fourteen days plus two reviews. Second, stage 2 is where most of the calendar goes, and it is the only stage entirely in your hands. The fourteen days count from when twelve testers are opted in, not from when you created the track — the full requirement is here.

What slows a decision down

Google does not publish a list, so treat these as the things that are known to cause trouble rather than a guarantee of speed if you avoid them.

  • Thin answers on the application. The form asks about your closed test, your app and your production readiness. Vague answers give the reviewer nothing to approve. How to answer each question.
  • A test that does not look like real use. Twelve accounts that installed once and never opened the app again is exactly what the requirement exists to catch.
  • Unfinished App content declarations. Data safety, content rating, target audience and the other declarations have to be complete before you can publish, so finish them during the test, not after approval.
  • Policy problems in the app itself. A policy issue found at this stage is a rejection, not a delay, and it is the most expensive thing to discover late.

What to do while you wait

  1. Keep the closed test running. Do not remove testers or end the track. Keeping everyone opted in until the decision costs nothing.
  2. Keep shipping to the closed track. Fixes from tester feedback are evidence of real testing, and a new build does not restart anything.
  3. Prepare the production release. Store listing, screenshots, release notes and a signed build ready to go, so stage 5 starts the day you are approved.
  4. Plan for a refusal without expecting one. If the answer is no, the email says why, and the fix is usually more or better testing rather than a new app. What to check if access is denied.

Next steps

Still need testers? Get 12 testers for your closed test through a free test-for-test exchange - you test another developer's app, they test yours, and every opt-in is verified.

Common questions

How long does Google take to review a production access application?
Google's own wording is that review usually takes seven days or less, but can occasionally take longer. The result is emailed to the Play Console account owner.
Should I stop my closed test while I wait for production access?
No. Keep every tester opted in and keep the closed track running until production access is granted. The application is judged on your testing, and there is nothing to gain from ending it early.
Once production access is granted, is my app live?
Not yet. Production access lets you create a production release. That release is then reviewed like any other, so plan for one more review before the app is public.

Apps currently in closed testing

Real developers running the test described above. Test one, and get testers for your own app back.

Closed testing

In Between is a free card game. Join the group, opt in, install, open it and play a hand. Keep it 14 days. Not available in South Korea. I test your app back the same day.

Games

Available in all countries

Open to testers · 14-day test

Closed testing

# BAYAA — Closed Testing: Instructions for Testers Thank you for participating in the BAYAA (بياع) closed testing program. BAYAA is a Mauritanian marketplace designed to connect customers with shops, restaurants, pharmacies, hotels, and service providers. ## 1. What testers are expected to do - Install BAYAA through the official Google Play closed-testing link. - Keep the app installed throughout the 14-day testing period. - Open and use the app regularly during the testing period. - Create an account and test registration and login. - Browse available shops, products, and services. - Test search and navigation. - Test merchant features if you have a merchant account. - Check WhatsApp contact options where available. - Report bugs, errors, confusing screens, and suggestions. ## 2. What feedback should you provide? Please tell us: - What worked correctly? - What did not work? - Were any pages slow or difficult to use? - Did you experience crashes or unexpected errors? - What features would you like us to improve? Honest feedback is very important. You do not need to give positive feedback if you encounter a problem. ## 3. Important testing rules - Use the app with your own tester account. - Do not share your login credentials. - Do not enter real payment or sensitive personal information. - Do not make fake purchases or transactions. - Do not uninstall the app during the testing period unless instructed. - Keep your Google Play testing enrollment active. ## 4. Reporting problems Send your feedback and screenshots of errors to the BAYAA development team. Thank you for helping us improve BAYAA and prepare it for its official launch in Mauritania. **BAYAA — بياع | Supporting Mauritanian Businesses**

Shopping

Available in all countries

Open to testers · 14-day test

Closed testing

PocketLedger helps you know your money and own your month — without handing your financial life to anyone. Everything stays on your phone. There is no account to create, no bank login, no SMS reading and no internet access at all. PocketLedger works fully offline. TRACK EVERY RUPEE (OR DOLLAR, EURO, POUND) • Add income and expenses in seconds, with category, account, date, merchant and notes • Mark refunds so they reduce your spending instead of counting as income • Search by merchant or note, filter by type, and tap any category to see its transactions for the month • INR, USD, EUR and GBP supported — amounts in different currencies are never mixed or converted SEE YOUR MONTH AT A GLANCE • Net cash flow, total income and total expenses for any month • Spending by category with an interactive chart • Recent transactions and account balances on one screen BUDGETS THAT KEEP YOU HONEST • Set a monthly limit for any category • See what you have spent, what is left, and when you go over ALL YOUR ACCOUNTS • Cash, bank accounts, UPI, credit cards and wallets • Pick from popular banks (SBI, HDFC, ICICI, Axis, Kotak and many more) and UPI apps, or type any name • Live balance for every account NOTHING IS EVER LOST • Every transaction keeps a full version history: see exactly what changed, when • Deleted transactions can be restored • An activity log records every add, edit, delete and setting change PRIVATE BY DESIGN • No sign-up, no ads, no tracking, no analytics • No internet permission — your data physically cannot leave the app • Not backed up to the cloud PocketLedger is a personal budgeting and expense-tracking tool. It does not offer loans, payments, banking or investment services and does not connect to any bank. Made by Technopreneurs Technolabs.

Finance

Available in all countries

Open to testers · 14-day test

Related guides

May we use analytics and ad measurement? Analytics (Vercel, and Ahrefs on our public pages) count page views without cookies. Ad measurement lets Google's tag on our public pages see which visits came from our Google ads, using a Google cookie. The site works the same either way. Cookie Policy · How Google uses data ·