Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Google Play says my app is out of date and warns about the target level

Short answer

Google requires new apps and updates to target a recent Android API level. An existing app below the required level stays installed for current users but stops being offered to new users on newer Android versions. Look at the warning on the Policy status page, note any extension option, and have the app updated and tested.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The Play Console shows a warning that my app does not meet the target API level.
  • I cannot upload an update because the console rejects the build.
  • Google emailed me that my app may become unavailable to new users.
  • New customers with recent phones say they cannot find my app.
  • My developer says the app has to be rebuilt just to stay in the store.

Why does this happen?

  1. Google raises the minimum target level over time

    Google's help page says new apps and app updates must target a stated recent Android API level to be submitted to Google Play, and that existing apps must meet a lower stated level to remain available to new users on newer Android versions.

  2. An app below the level shrinks its audience

    Google states that apps targeting a lower level are only available on devices running the same or lower Android versions, so they are no longer discoverable to new users on devices with newer Android versions.

  3. People who already have the app are not affected

    The same page says users who already installed the app can still reinstall and use it. The loss falls on new customers with newer phones.

  4. Raising the level changes how the app behaves

    Android documents behaviour changes that apply only once an app targets a new level, for example screen layout, back navigation and orientation on large screens. So the work is an update and a test, not a number change.

  5. The app was left without maintenance

    A warning is easy to miss when nobody is watching the Console, for example after a developer has left. The notice then sits unread until the deadline is close.

What can I do about it today?

  1. Open the warning and read it fullyIn the Play Console, open the Policy status page and the warning for your app. Write down which level it asks for and which app.
  2. Look for an extension optionGoogle's page says impacted apps can receive a link to an extension request form through Notifications, reached from the warning's details page. Check whether yours shows one and note the date it gives.
  3. Do not unpublish or delete the appExisting users keep the app. Removing it throws away reviews and statistics for nothing.
  4. Find out who can build the appAsk who has the source code and the signing details. If nobody can build an update, that is the first problem to solve.
  5. Check the app on a recent phoneInstall it from the store on a current phone and use the main screens. Write down anything that looks broken; it helps whoever updates it.
  6. Add the Console to an email you readMake sure policy emails reach a person who will open them, not an old developer's inbox.

When should I bring someone in?

  • No one on your side can build and upload a new version.
  • The warning has a deadline and the app earns money from new users.
  • The app uses old libraries that may not build against the newer level.

How do I handle it?

  1. Read the warning and the appI check which level is asked, what the app targets today and what libraries stand in the way.
  2. Take a backup firstThe source code and signing details are saved before any change is made.
  3. Raise the level and fix what it affectsI update the build, then go through the behaviour changes documented for that level and repair the screens and flows they touch.
  4. Test on recent phonesI test the main journeys on recent Android versions before the update goes anywhere near the store.
  5. Release in stages and keep a way backThe update goes to a test track first, then to production, with a tested rollback ready.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Will my current users lose the app?

According to Google's page, users who already installed an app can still reinstall and use it. New users on devices with newer Android versions stop seeing it.

Can I get more time?

Google's page describes an extension request, reached from the warning on the Policy status page for impacted apps. Whether it is granted is Google's decision.

Is this only a number I can change?

No. Google documents behaviour changes that apply when an app targets a new level, so each update needs testing.

Does this apply to every kind of device?

Google lists different levels for some device types, such as Wear OS, TV and cars. Check the table on its page for your app.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.