How to Publish an App on Google Play (and Fix Rejections)

20 min left0% read
How to publish an app on Google Play: Android robot, a phone with an app that is now live, and the Google Play logo
20 min left
  1. How Strict Is Google Play Review Now?
  2. What You Need Before You Publish on Google Play
  3. How to Publish an App on Google Play in 7 Steps
  4. How Long Does Google Play Review Take?
  5. The Most Common Google Play Rejection Reasons and How to Fix Them
  6. "Your App Requires More Testing": How to Fix a Production Access Rejection
  7. What to Do After a Rejection: Fix, Resubmit or Appeal
  8. Publish It Yourself or Hire an Android Team?
  9. Frequently Asked Questions

Key Takeaways

1 min summary
  • Paying the $25 fee is important to get started on Google Play, but approval, not the upload, is the hard part for most new apps.
  • While your app is live, you will need to keep meeting the target API level, keep your Data safety form accurate, pass review on updates, and keep policies current.
  • While organization accounts aren't required to run a closed test, new personal accounts need 12 testers opted in for 14 days in a row before production.
  • Production access review usually takes seven days or less, but each new release still goes through app review, which can take up to seven days.
  • Initially, your app may get rejected because one wrong form, like the Data safety section, can block the whole update.
  • However, many rejections can be fixed quickly if you read the Policy status page, fix the cause and only then resubmit or appeal.
  • A new personal account should plan for about 4 to 5 weeks, but for payments, user data or tight deadlines, you'll want an experienced Android team.
Summarize with AIGet the key points of this post

Publishing on Google Play can be a great first launch, if not a full-time stream of downloads, for many app makers. Google reports it stopped over 1.75 million policy-violating apps in 2025, saying it runs more than 10,000 safety checks on every app it publishes.

With Google Play available pretty much anywhere, the Google Play Store is open to new developers pretty much everywhere, so long as they have a working app and can meet the policy requirements.

But on top of the right code, a $25 developer account, and patience, you will have to pass Google Play review. Run by Google’s own scanners and reviewers, Play Console will accept or reject your app’s release based on the results.

This article will cover the ins and outs of how to publish an app on Google Play, plus how to fix the rejections that stop most first launches.

How Strict Is Google Play Review Now?

Google Play review is a screening step that all new apps and updates must complete.

New developers must agree to the Google Play Developer Program Policies during sign-up. The process involves passing a policy review for your app’s content and data use and, for new personal accounts, a closed test with real testers.

The process isn’t meant to be a burden, but rather to protect the user experience and safety for Google Play users.

Google is checking for major things like malware, hidden data collection, and other deceptive behavior, or serious problems like apps that crash on launch.

Google will send the results of a review only to the developer account. They are not usually released publicly.

Google Play review numbers: 1.75 million policy-violating apps stopped, 255,000 apps blocked from excess data access, 80,000 developer accounts banned
Google’s own numbers show how many apps it stops before they go live. Source: Google.

There are two (2) key parts of Google Play review:

There may be differences in some app categories as to what Google checks for, depending on internal standards plus local laws and rules for health, finance and kids apps.

Depending on the category, the rules could be more strict.

1. Policy and Content Review

Google uses automated scanners and human reviewers to check your app bundle and store listing, which covers your full app content including permissions, data use, and any ads. It will also verify your app targets a recent Android version, at least Android 16 (API level 36) for new apps and updates, or API 35 for Wear OS and Android Automotive OS apps.

2. Testing for New Personal Accounts

Google also uses a closed testing rule to examine new personal developer accounts. Google does not have one official fixed number of builds it examines.

The store has said that whether the testing rule applies depends on when the account was created and the type of account. Every personal account created after November 13, 2023 has to run a closed test with at least 12 testers for 14 days in a row.

Even if you have an older personal account, it does not mean that Google will skip a careful review. In fact, organization accounts have been left out of the rule that holds new personal accounts back from reaching production on their first try. Google, and most other app stores, may not mind that your first build uses a stock font and a gray splash screen.

But they do worry about policy problems that would put user safety at risk, and serious ones are disqualifying. This may include malware, hidden data collection, or deceptive behavior. If there are open policy issues on your account for any of these, Google may reject your app. However, if the issues are fixed or you clear them on appeal, it’s worth submitting again afterward.

What You Need Before You Publish on Google Play

The minimum Google Play requirements may seem long but are quite simple for an app store. Here’s what you have to do to clear Google Play’s publishing rules.

Google Play target API level by device: phones and tablets API 36, Wear OS and Automotive API 35, TV and XR API 34
Minimum target API level for new apps and updates, by device type. Source: Android Developers.

1. Personal vs. Organization Account

Not only does Google care about the app’s quality, but they also care about the developer account. The mix of a verified developer and a stable app gives users the best result. Like apps, accounts have to go through a verification process. Developers must have their identity verified with a government ID or, for organizations, a D-U-N-S number. This is to confirm the account is real enough to publish apps to Google Play users.

Also, like apps, Google cares about the type of the account. Google wants businesses on organization accounts so users see the real company name and are less apt to be misled.

Your account verification will determine if your account is eligible, but you can still check the account types on Google’s help page to see which one fits.

2. Fee Requirements

Wondering how much it costs to publish an app on Google Play? You’re not the only one! Google has a simple fee for developers.

For example, even though Apple charges $99 a year to list apps, Google only charges a $25 one-time registration fee, but you must pay it with a credit or debit card.

Personal Accounts

Even though you only have to pay $25 to open a personal account, that isn’t enough to get your app live. New personal accounts must verify a government ID and an Android device and run a 14-day closed test with 12 testers. So if you’re verified but don’t have 12 testers yet, you won’t qualify for production until you have the needed testers in your test or open an organization account.

Organization Accounts

If you’re on an organization account, the 12 testers rule doesn’t apply. However, you’ll need a D-U-N-S number and a verified business, whether you’re a team of 2 or 200. This ensures safety for you and your users.

3. App Files

To qualify for Google Play, you must provide specific files for review. You’ll upload the files to Play Console when you create the app. All new Google Play apps must submit the following items:

4. Data Safety and Policy Declarations

To qualify for Google Play, you must complete the App content section. This is to ensure your app is not a threat to users and is honest about data.

The declarations must show that your app has not hidden any data collection, ads, or sensitive permissions. Your Data safety form must also show you don’t share user data without saying so, including through third-party SDKs or ad networks. The review goes back over each declaration for your app and your store listing.

5. Target API Level

While Google Play apps must pass rigorous policy and content checks, your build must also meet a target API level. This is because Google pushes apps on the store to use recent Android security and privacy features.

The target API check is simple and can be handled in Android Studio or your Gradle file. Google has a specific target API rule the build must meet proving the app supports a recent Android version. Once updated, you must upload the new build to Play Console.

Most apps need to update their target API level every year.

How to Publish an App on Google Play in 7 Steps

Publishing an app on Google Play consists of setting up your developer account, building and testing your app, and then sending it to review.

How to publish an app on Google Play in 7 steps: developer account, app and listing, App content, build and internal test, closed test, production access, release
The order of the 7 steps in Play Console, from account to release.

Step 1: Create Your Google Play Developer Account

In order to publish on Google Play, there are some general account requirements.

  • Minimum age of 18 to create a developer account.
  • A one-time $25 registration fee for the account; a D-U-N-S number required for organization accounts.
  • Pick an account type. Requirements may vary by type, but in most cases a solo developer starts with a personal account.
  • Provide the necessary contact information, including legal name, address, and a verified phone number.

Step 2: Create the App and Store Listing

You will also need to provide the following details:

  • App name and default language for the app you will publish (you must also say if it’s an app or a game).
  • Free or paid status for your app (important as a free app can’t be changed to paid later).
  • Store graphics. Must include an app icon at 512 x 512 pixels and a feature graphic at 1024 x 500. (Phone screenshots that match the real app will be needed for your store listing too.)

Step 3: Complete the App Content Section

You will need to actively complete the App content section when you set up your app in Google Play Console. Beyond the Data safety form previously listed, Google will also ask about your ads, target audience, content rating questionnaire, and app access.

You must log into Play Console to give answers and fill out all declaration forms.

Step 4: Build, Sign and Run an Internal Test

Build the release bundle and sign it, you can do everything in Android Studio or from the command line. There’s no extra cost to use Play App Signing, once you’ve enrolled the app and uploaded the first bundle, Google keeps your app signing key for you!

You will need your package name, your upload key, and your version code. These three items will identify your app on Google Play, prove the update comes from you and allow you to ship new versions later.

Google says your internal test should only take minutes to reach up to 100 testers. The sooner you can test your app, the better!

Once internal testing is live, you’ll be given an opt-in link from Play Console to share with testers on your team. Do not use your own Gmail as the only tester account. It’s, at best, a weak test of your app, and, at worst, you’ll miss the bugs real users hit.

It should only take a few minutes for your internal test build to show up for testers once you’ve rolled it out in Play Console.

Step 5: Run a Closed Test With 12 Testers

Setting up a closed test is simple, create the track in Play Console, and wait for your testers to opt in! The testing page will show you things like:

  • How many testers have opted in
  • Which release is on the track
  • Pre-launch report results for your build
  • How many days your test has run

Once you hit 14 days with 12 testers opted in, start heading to the Dashboard so you can apply.

Step 6: Apply for Production Access

When your test passes 14 days, you can pull up the Apply for production form for that particular app in Play Console and answer each question as you go through the form.

The form helps you apply efficiently because it asks about your closed test, your app and your production readiness. If you can’t find a tester’s comment or it’s not in your notes, you can check the private feedback testers left on Google Play. Or, you can report what you fixed after testing.

Step 7: Release to Production

Make your release and roll it out when you want!

Free consultation
Want Your First Google Play Release Done Right?

Launching on Google Play is fairly easy when our Android team handles the testing and release.

  • A written scope and cost range
  • Fixed price or hourly, your choice
  • 5.0 rating from 250+ client reviews

How Long Does Google Play Review Take?

Google Play review typically takes up to seven days to process. Extended reviews can slow the process. If you’ve waited more than seven days, it’s worth contacting Google Play developer support. Their help center takes follow-up requests for the app review.

StageTypical time
Internal testMinutes
Closed test (new personal accounts)14 days minimum
Production access reviewUsually 7 days or less
App reviewUp to 7 days
UpdatesAs soon as possible
Google Play review time for a new personal account: closed test 14 days, production access review up to 7 days, app review up to 7 days
How long each stage can take for a new personal account, in days. Source: Play Console Help.

Why Your Google Play Review Might Be Delayed

While it usually takes seven (7) days or less to get your review results, there are delays at times.

Here are some of the more common reasons for review delays.

  • Extended reviews: Some developer accounts get additional screening which can prolong the review process. For new personal accounts, for example, the production access review comes first and usually takes seven days or less.
  • Manual review: Google’s reviewers may check sensitive permissions and declarations by hand when screening apps, which can delay your results.
  • More details needed: At times, the review team may need more details to complete your review, such as login details for a test account. You’ll be contacted by email. While you wait for review results, check your email and Play Console inbox every day, spam folders too. Make sure you reply promptly to any messages.

How Often Does Google Review Apps?

Google reviews an app at its first release and then every time you submit an update. In some categories, Google may choose to review apps more closely. And Google can choose to review a live app at any point.

In our view, reasons that Google may check apps more closely may include repeated user complaints, barely passing an earlier review (with warnings left on the account), or a sudden change in permissions.

The Most Common Google Play Rejection Reasons and How to Fix Them

Here are some of the most frequent reasons that Google Play apps get rejected. Often, it’s related to an accidental break of Google Play’s Developer Program Policies.

Common Google Play rejection reasons and where to fix each one in Play Console
Each rejection reason and where you fix it in Play Console.

1. Crashes and Broken Features

Unstable builds are a common reason apps get rejected. This includes crashes on launch, blank screens, broken log-in, and features that don’t load. Many developers forget about older phones or forget to test a fresh install before they submit.

These rejections are often quick and easy to fix. You can skip the hassle though by fixing the crashes in your pre-launch report before you submit.

2. Data Safety Form Doesn’t Match the App

A wrong Data safety form will stop you from getting your update approved.

Although an initial Data safety form was needed to get on the store, per Google’s policy the form has to match every new version you ship. If an SDK starts collecting new data, it can get your update rejected.

Approval, depending on the issue, can still be possible though if you update the form to match what the app and its SDKs collect.

3. Missing Privacy Policy or Account Deletion

If your privacy policy link is missing or broken, you could be rejected.

If users can create accounts, your app needs in-app and web account deletion. It’s important to read the policy closely. Also, check the help center pages on the User Data policy and email support if you have more questions.

4. Sensitive Permissions

Photo and video permissions can be a pain in the neck to Android developers and other app makers, or anyone who needs access to a user’s photo library.

With the photo and video permissions policy, you are asked to use the Android photo picker in order to protect user privacy. If your app requests READ_MEDIA_IMAGES or READ_MEDIA_VIDEO without a core need (like a gallery app), then your app could get rejected.

Make sure to remove permissions you don’t need from your manifest, and consistently check what your SDKs add to it in the same way.

5. Target API Level Too Old

Targeting an old Android version or skipping updates too long can lead to a rejected update, and even keep your app from new users.

Google will reject your update if your app targets an API level below the yearly requirement, which is Android 16 (API level 36) for new apps and updates.

Of course, these deadlines may be hard to track and a library may hold your upgrade back.

You do have the option to request an extension in Play Console when Google opens the form. If you follow the rules and ship the update in time, you will likely keep your app available.

6. Minimum Functionality and Webview Apps

Google expects its developers, publishers, and other app makers to adhere to the Minimum Functionality policy. This prohibits empty, broken, or very thin apps, apps that only load a website, or apps with no real purpose.

7. Misleading Store Listing

Google will reject your app if reviewers find your store listing misleading. Unless your screenshots show features the app doesn’t have, or your listing (which reviewers compare to the app) uses another brand’s name, it can be hard to tell what they flagged.

If there are no other policy issues and you follow up with Google support, Google may approve the fixed listing.

8. Copying Other Apps or Brands

Do not use names, logos, or content you don’t own. This may include another brand’s trademark (names, icons, characters) or copying an app’s look after it’s already on the store. Do not use a famous brand for any reason in your listing, unless it’s your own brand or you have written permission.

9. Selling Digital Goods Outside Play Billing

If your app sells digital goods, such as subscriptions, coins, or premium features, and the purchase skips Google Play’s billing system where the payments policy requires it, Google can take action against your app.

10. No Login for the Reviewer

A missing test login is one reason an app may find its review stuck or even rejected. This may include a login screen with no demo account, a code sent only to your phone, or features locked behind a paid plan (for the reviewer too). Fill out the App access section and don’t hide parts of your app from the review.

Talk to our team
Stuck on a Google Play Rejection?

Send us the rejection email. Our Android developers find the cause, fix your app and resubmit it for you.

5.0 from 250+ client reviews

“Your App Requires More Testing”: How to Fix a Production Access Rejection

A denial can come without much warning. When possible, Google may tell a developer what was missing from their closed test, but this doesn’t always happen. Typically, developers will find out their access has been denied when they get an email saying their app requires more testing to access Google Play production.

You will receive a message in Play Console, such as a note asking you to keep running your closed test.

Google Play closed testing: 12 testers opted in for 14 consecutive days before you can apply for production
Each tester must stay opted in for 14 days in a row. Source: Play Console Help.

What Happens to Your App if Production Access Is Denied?

If you get denied production access, you are not banned from Google Play and its other tracks like internal and closed testing. Google specifically is not rejecting your app; it’s asking for a better closed test of the same app.

Some developers may have a good case for why their app was ready if their testers did use it. You can add more detail in your next application or contact Google Play developer support.

This would be for rare cases, like your testers were using the app every day but your answers on the form were too short. This could make a solid argument for being approved on your next application.

What to Do If Your Access Is Denied

If you do get denied production access and want to publish your app on Google Play, here’s how to proceed.

  • First, find out why you were denied. What does the email from Google say?
  • Check your tester count. Replace any testers who opted out.
  • Contact Google Play developer support. Ask a question through the Play Console Help Center.
  • Review the app testing requirements. It’s a wealth of help on why testing falls short and how to fix it.
  • Share what your testers found. Be specific, honest, and detailed.
  • Ship a new build to the closed test.
  • Wait patiently. Don’t apply again until your testers have used the new build for a while.

Finishing any or all of these steps does not guarantee your app will get production access. However, you have to go through them to try. For many denied developers, it’s simply a matter of running a better test and being patient.

How to Avoid a Production Access Rejection

The simplest way to deal with a production access rejection, of course, is to avoid being rejected in the first place. These tips show how to keep Google from turning down your application.

1. Recruit more than 12 testers

The minimum number of testers you need is 12 opted in, but plan for around 15 to 20, or whatever covers the testers who drop out. For example, if 3 testers opt out halfway, 15 testers would still keep you at the minimum.

2. Keep testers active

Keep your testers engaged. Sometimes, a tester going quiet is unavoidable. They get busy or they’re so stuck at work that there’s no way they open the app that week. But do all you can to keep the activity up.

If a tester stops opening the app after they’ve opted in, ask them to try one new feature on their side each day.

If a tester is unhappy about the app (i.e., a screen crashes or they can’t log in), it’s smart to proactively fix it and let them know.

3. Respond promptly to feedback

Testers may send you a crash report or a comment to let you know a feature is broken. These usually come when a tester hits a serious bug, and often, you will see a crash in Android vitals or the pre-launch report that gives you a summary of the problem.

Be sure to reply to this feedback so that you keep a document trail. Follow up with a new build quickly, ask for more details, and note any changes you made.

4. Proactively improve a basic first build

If your first build is basic, proactively improve it during the test. For example, the Todochi team, four brothers from the Philippines, said Google “could not detect enough engagement” from testers of their basic first build and denied their first application.

They added features and onboarding, kept testing as Google suggested, and treated testing as a chance to improve the app.

What to Do After a Rejection: Fix, Resubmit or Appeal

If you do get a policy rejection, it’s not always the end of the road. You can fix it. Many rejected developers are able to resubmit or appeal Google’s decision and stay on the Play Store.

What to do after a Google Play rejection: rejected, removed or suspended, and the next step for each
What to do next depends on the status Google gives your app. Source: Play Console Help.

After Google notifies you that your app is rejected due to a policy issue, Google should name the policy in your email and on the Policy status page. Look it over for the exact issue.

If you find errors, you can appeal the decision’s findings.

  • Rejected: Fix the issue before you send a new update. Your last approved version stays live on Google Play while you fix it.
  • Removed: Your app is gone until a compliant update is submitted. Fix the policy violations first, then upload a new version and send it for review.
  • Suspended: Select Appeal on the Policy status page in Play Console. Send a short, clear note on what changed and why the app follows the policy.

Some developers do successfully appeal an inaccurate rejection. Keep in mind, though, that Google could still reject your app. Google can reject apps that pass an earlier review, or that successfully overturn one decision on appeal.

Other Options While You Wait

Getting rejected from Google Play is no fun, but it isn’t the end of the world. Rejected developers can reach out to Google Play support for help. Often, rejected developers fix their apps and get them approved again.

While you wait, you can list your app on other Android app stores like Samsung Galaxy Store or Huawei AppGallery. For any Android developer, it’s wise to have more than one store, your main store and a back-pocket option. This way you can grow your reach and total download potential.

Publish It Yourself or Hire an Android Team?

For the most part, publishing a simple app on Google Play takes a few weeks on your own. For some, with an older account, only a couple of days. It’s a process that every developer must go through to ensure that apps give users a safe experience.

The review is run by Google’s own scanners and reviewers looking for policy breaks or unstable builds. Not every bug will show up in review. And you can appeal decisions you think are wrong.

Simple apps often pass the content review portion, and apps that get stuck often do so because of testing or data forms. For apps with payments, user data, or a launch deadline, luckily, you can hire an app developer or an Android app development team to handle it. While it’s not free, at least you are less likely to lose weeks to rejections.

Publish an app on Google Play yourself or hire an Android team: simple apps versus apps with payments, user data or deadlines
When to publish on your own and when to bring in a team.

The process may seem stressful, but for most developers, it’s a straightforward process that they get through with a little planning.

Free consultation
Need an Android App Built and Published?

Ready to launch on Google Play? Apps start from $15,000, or $25 to $50 an hour, and you own the code.

  • A written scope and cost range
  • Fixed price or hourly, your choice
  • 5.0 rating from 250+ client reviews

Frequently Asked Questions

Can I publish an APK, or do I need an AAB?

No, the upload format for new apps is the Android App Bundle (AAB), not the APK. Google Play is one store, and the AAB is the format it builds APKs from. It has the same upload rules for all new apps on the store.

Do organization accounts need 12 testers?

Google applies the testing rule to new personal accounts, so organization accounts should not need it.

A personal account is one owned by an individual developer and created in their own name. An organization account is one owned by a business and verified with a D-U-N-S number, and is seen more as a company publishing an app.

Google used to ask for 20 testers on new personal accounts, but no longer. Since December 2024, the rule has been 12 testers opted in for 14 days in a row.

Why is my app stuck in review on Google Play?

Wait times for review tend to take longer for certain developer accounts and for apps with sensitive permissions.

For certain accounts, Google may take longer to check the app and its declarations. For sensitive permissions, this is because Google’s policy limits which apps can use them and reviewers check each declaration.

How do I check my app’s review status?

When you have submitted the release, open your app in Play Console to see its review status under the app name.

How do I appeal a Google Play rejection or suspension?

While Google has an official appeal process, it isn’t the same for every action. There’s no single form for all of it. But developers can successfully get rejected or suspended apps back.

If you’re a rejected developer, start with the Policy status page. Find out what happened, and provide any evidence or changes to show why your app should be allowed back.

Can I publish an app on Google Play for free?

Google charges a one-time $25 fee for the developer account, and there are no yearly fees, so you don’t have to worry about renewal costs.

Does Google take a cut of in-app purchases?

Google charges a service fee on paid apps and in-app purchases. In most markets enrolled developers pay 15% on the first $1 million a year and on subscriptions, with different rates in the US, UK, EEA, Australia and Japan.

Have a project in mind? Get a free consultation.

Tell us what you want to build. We reply with next steps, a rough timeline and a cost range.

(800) 995-3369

    Matthew Jones
    About the author
    Matthew Jones

    Matthew Jones supports Octal Digital as a Digital Strategist and trusted technology advisor, helping guide clients through scalable solutions, emerging tools, and smart development strategies that align with business goals and growth.

    Let's Connect

    With Our

    Experts

    Outstanding Reviews on Clutch

    5.0

    5-star client rating

    Get valuable consultation form our professionals to discuss your project idea. We are here to help you with all of your queries.

    Clutch

    Top 1000
    Companies

    Right Firms

    Top App development
    Company 2024

    Good Firms

    Top Software
    Developer Companies

    Schedule a Free Consultation