AppReviewFix
Guideline library
Google Play — Technical Compliance

Target API Level — Target API level requirements

Reviewed 10 October 2026Official source: Google Play Developer Program PoliciesTopic overview: The review process, app quality and enforcement
What this guideline means

Google requires apps (and updates to existing apps) to target an Android API level released within roughly the last two years — apps targeting older levels are blocked from being updated or newly published.

Why apps actually get flagged

Almost always simply a maintenance gap: an app that hasn't been rebuilt against a current Android SDK in over a year, unrelated to any content issue.

A real example

"This app is not compliant with Play policy regarding target API level and cannot be published until you update targetSdkVersion, per the Target API Level requirement."

The short version, in more detail

Google Play requires new apps and app updates to target a recent Android API level, and it raises the bar roughly once a year, usually with a deadline around the end of August. If an app targets an older level, it may be blocked from publishing updates or from reaching newer devices. The requirement is a platform rule, so it is applied the same way to everyone.

What this guideline covers

  • The minimum target API level for new apps and for updates to existing apps.
  • Annual deadlines for raising the target level.
  • What happens to apps that do not meet the requirement, including limits on updates and visibility.
  • Whether extensions are available and how they are requested.

What usually triggers this rejection

  • The app's target SDK is below the level Play currently requires for new apps or updates.
  • The annual deadline has passed and the app is now blocked from updates or hidden from users on newer Android versions.
  • A framework or library pins an older target level.
  • The target was changed but the bundle Play is checking was not the updated one.

How reviewers evaluate it

  • The requirement is checked automatically when a release is uploaded.
  • There is no human judgement, so the outcome is predictable.
  • Play Console shows warnings ahead of deadlines and after they pass.
  • Existing installs keep working, but new releases are limited until the requirement is met.

Common misunderstandings

  • It is not a quality judgement. It is a technical requirement applied to all apps.
  • It does not remove existing installs. It restricts updates and discovery.
  • The required level is not fixed. It changes roughly each year, so old information can be out of date.

Common questions

How often does the required level change?

Typically once a year, with an announced deadline. Check Google's documentation for the current level.

Do cross-platform apps have different rules?

The same requirement applies, but the framework version in use can determine which target level is possible.

Are there extensions?

Google has offered extension requests in some cycles. Availability varies, so it is worth checking the current policy.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
2.1 — App Completeness2.2 — Beta testing2.3.1 — Hidden or undocumented features4.2 — Minimum functionality4.2.3 — App independence
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.