Weple

When the app works the same as ever and only the new users stop arriving

App Store Requirement Updates

We bring an app up to the version the stores now require, so you can publish again

The version the stores require goes up every year. Miss the deadline and the app keeps working for the people who have it, but nobody new can install it.

When review turns you away, or new installs quietly stop

Every year the stores raise the version an app has to be built against. Past the deadline, Google Play blocks new installs and the App Store refuses new builds. Everyone who already has the app carries on using it, so from the outside nothing looks wrong. That is why most people find out long after it happened.

What we do

  • Finding what is missing

    We check what version the app and its build tools are on, and write up exactly where they fall short of what the stores now ask for.

  • Moving up to the required version

    We take the app up to the version required, and handle the permission and behavior changes that come into force with it at the same time.

  • Checking the screens that shifted

    Building against a new version can change how the standard screen elements are drawn. We go through the app ourselves, find what moved, and put it back.

  • Through to a passed review

    Permission declarations, the data safety form, and the other items review stops apps on: we get those in order before submitting.

The record of what was done

What was missing, how far we moved it, and when the next deadline falls. This comes around every year, so next time that record is where to start.

How to start

  1. The app and its build settings

    Send the repository or the build settings and we tell you where the app falls short of what the stores ask for.

  2. Scope and timeline agreed

    How far to take it, and whether we submit it for you as well, are settled first. Nothing is charged until you agree to that.

  3. The update and the checks

    We move the version up, fix what broke, then go through the main screens to confirm they behave as they did before.

  4. Submission and handoff

    We put it up on the store, confirm it passed review, and hand it back with the record.

A good fit for

  • Anyone who has had a notice from a store saying new installs are blocked
  • An app stuck on a years-old SDK that can no longer publish an update
  • Anyone whose submission was rejected in review over the version it targets

Frequently asked questions

Does the app have to be rebuilt?
No. The existing code stays where it is. We change the build settings and the parts that break under the new version, and nothing else.
How long does it take?
It depends on how many versions behind the app is. One or two and it is quick; if it has sat still for years, there is that much more to fix. We look first, then tell you.
Do we have to hand over the store account?
Only if you want us to submit it. Otherwise we hand you the build and you upload it yourself.
When is the deadline?
It differs by store and it moves every year. We check what your app is caught on and when its next deadline falls, and tell you.

Sort it out before new installs are blocked

Send the app's repository or its build settings and we start by checking where it falls short.

See all services