Lo Resolví
Tech

Google Play closed testing and what can get your app rejected

What I went through before applying for production on Google Play. The 12 testers, the crashes that almost stopped me and the policies that reject apps.

In this article
  1. What closed testing is
  2. The crashes that almost stopped me
  3. What Google rejects most often in apps like mine
  4. Your privacy policy has to match what the app actually does
  5. My checklist before applying for production
  6. After approval

Finishing an app is not the same as being allowed to publish it. If your Google Play developer account is personal and new, you first have to pass a closed test and then apply for permission to reach everyone. I just went through that process. Here is what worked for me and what almost stopped my release.

Android Studio screen showing Kotlin code for an app ready to build and publish

What closed testing is

It is a version of your app that only people you invite can download. You send them a link, they accept to become testers and they install it from Google Play like any normal app.

For personal accounts created after November 13, 2023, Google asks for something specific. At least 12 testers opted into the closed test for 14 days in a row. Only then can you apply for production access.

Twelve people sounds easy. It is not. They actually have to install it and stay in the test for all 14 days. I shared mine with classmates and people I knew, and explained what it was for. Without that context, people install it, glance at it and leave.

The crashes that almost stopped me

Before applying for production I checked my app’s crash reports. I got a scare. Over 30 days there were 75 crashes across 10 people. Only 64 % of users had not hit a single crash.

Google looks closely at stability. With those numbers they would probably have said no. So I stopped and fixed the crashes first.

There were two bugs. One screen kept trying to read its state after closing, causing the app to crash on exit. The other was the font. The app downloaded it from the internet on launch, and without mobile data it crashed. The fix was bundling the font inside the app.

I uploaded the fixed build to closed testing and waited a few days with clean reports. Then I applied for production. They approved it.

What Google rejects most often in apps like mine

My app uses rules from several public universities to calculate grades. That carries a risk I did not know about.

Google has strict rules for apps that display government or public institution information. If your app is not official, you have to state that clearly and show where the rules come from, with links to official pages. Otherwise you can be flagged for impersonation.

I prepared for that before it could happen. Here is what I put in place.

  1. A visible notice stating that the app is unofficial and does not represent any institution.
  2. Links to the official pages of each university in the store listing, inside the app and on the privacy policy page.
  3. Removing institutions from the app and texts whose rules had not been verified yet.
  4. A short explanation for the review team inside Play Console’s special review instructions.

Your privacy policy has to match what the app actually does

I caught this mistake during a pre-production check. My app always sends crash reports and usage analytics. Yet my privacy policy claimed that was optional and turned off by default.

A reviewer who reads your policy and sees different behavior in the app has a clear reason to reject it. The same goes for Play Console’s Data Safety form. What you declare there, what your privacy policy says and what the app does all have to match.

My checklist before applying for production

  1. Twelve real testers, told what the test is for, staying opted in for 14 days in a row.
  2. Crash reports checked. If the app crashes, fix it first and wait for clean reports.
  3. The app works offline wherever it is supposed to work offline.
  4. If you show public institution data, add a non-official disclaimer and links to official sources.
  5. The privacy policy, the Data Safety form and the app all say the same thing.
  6. Clear instructions for the reviewer if any feature is not obvious at first glance.

After approval

Getting approved does not mean launching that same day. My app is approved and three of us are still testing it. It is the best time to inspect what is left, because any bug still affects nobody. I wrote about that in updating an app in closed testing and with real users.

Checked on November 21, 2026. The 12-tester requirement is in the Play Console help page for new personal accounts. Rules for public institution data are in the requirements for apps that communicate government information.

Comments

Write a comment

Comments are reviewed before they are published. Read the Privacy policy.

← Newer post