Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Customers are stuck on an old version of my app and I need them to update

Short answer

A forced update has to be built into the app. On Android, Google's in-app updates offer an immediate flow that requires the user to update before continuing. Firebase Remote Config can target users by app version without a new release. Versions already installed without that code cannot be forced, only reached through the store and your customers.

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

Does this sound like your situation?

  • A server change broke the old versions of the app, but some users never update.
  • A security fix is released and many people still run the version without it.
  • Support keeps getting problems that were fixed months ago.
  • I cannot tell how many people run each version.
  • My developer says old versions cannot be forced to update.

Why does this happen?

  1. Stores update apps only if the user allows it

    Google notes that some users enable background updates on an unmetered connection while others need to be reminded to install updates. So a fix in the store does not reach everybody by itself.

  2. A forced update needs code inside the app

    Google's in-app updates feature supports two flows. A flexible update downloads in the background while the user keeps using the app. An immediate update is a full-screen flow that requires the user to update and restart the app to continue, which suits updates that are critical to the core function. It works on Android 5.0 or higher and only on Android phones, tablets and ChromeOS. An old version that never contained this code cannot start it.

  3. A remote switch can tell old versions what to do

    Firebase Remote Config changes how an app behaves without a new release and can target users by app version. It also supports gradual rollouts. The app has to contain the Remote Config code, and Google warns that its values are readable by end users, so no secrets belong there.

  4. Your server can be the second line

    If the back end refuses requests from versions it can no longer serve, the old app can at least show a clear 'please update' message instead of failing in confusing ways. Whether that is possible depends on how the app was built.

What can I do about it today?

  1. Find out which versions are out thereAsk your developer, or look in the store consoles, for how many users run each version. You need this number before deciding anything.
  2. Decide what you actually needWrite one sentence: why must this version stop being used? A broken feature, a security fix and a legal change need different levels of force.
  3. Ask your developer if the app can ask for an updateA plain question: does the current version contain an in-app update prompt or a remote switch? If not, the next release should add one.
  4. Release the fixed version normally firstCheck that the new version is live in both stores before any message goes to customers.
  5. Tell customers through channels you ownEmail, a website banner or a message in your support replies can say 'please update in the store'. Keep it short and link to the store page.
  6. Do not switch off the old server yetClosing the old back end without warning locks out every user still on the old version. Plan the date with your developer first.

When should I bring someone in?

  • The old version loses data or causes wrong payments.
  • A security problem is fixed only in the new version.
  • The current app cannot ask users to update, so every future release has the same problem.

How do I handle it?

  1. Count versions and risksI read the usage data and the code to find which versions exist and what each one can still do safely.
  2. Add an update checkI add a version check to the app, using the store's own update flow on Android and a remote setting that both platforms can read.
  3. Keep the server compatible for a stated periodI plan with you how long the old back end keeps answering old versions, and write the switch-off date down.
  4. Test with a small groupThe prompt is tried on test devices and, where the setup allows, rolled out gradually before everybody sees it.
  5. Keep the next release the last painful oneOnce the check is inside the app, future versions can be retired in a controlled way.

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?

Can I force an update on iPhones?

I do not rely on an Apple feature for this. The usual way is for the app to check its own version against a setting you control and show an update screen that links to the store. That code must already be in the installed version.

What about users who ignore every message?

They stay on the old version until the app or the server refuses to continue. Whether to do that is a business decision, because it may lose customers.

Does a forced update need a store review?

The version that contains the update check goes through the normal store review like any release, and the store decides how long that takes. A remote setting afterwards does not need a new release.

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.

Next step

Want this off your desk?

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