The iPhone app demands an update nobody can install
Your task
It is 09:40. Your food delivery app runs on iOS and Android. At launch, the app checks a setting called min_supported_version. It fetches the setting from your remote config service at most once an hour and keeps the value on the phone. An app older than that version shows a full-screen "Update required" page with a link to its store, and nothing else works. This alert fires:
IosSessionsLow: iOS sessions 60% below this time last week for 10 minutes (threshold 40%)
What you see:
- iOS sessions began to fall at 09:15 and are still falling. Android sessions are down about 10%. API errors and latency are flat.
- Support has 190 tickets since 09:20. Most say: "It tells me to update, but the App Store has no update."
- The config audit log shows
min_supported_versionchanged from 5.2.0 to 5.4.0 at 09:12, by Dana, with the note "5.4.0 release day". - App Store Connect, Apple's release console, shows 5.3.1 live and 5.4.0 as
Waiting for Review. Google Play has had 5.4.0 live since 08:30, and updates there are climbing.
What do you change now, when will iPhone customers be back in, and what must be true before this setting goes up again?
It covers
- Mobile releases
- Remote config
- App store
About this question
The iPhone app demands an update nobody can install
Model answer
Free on every accountFirst move: set min_supported_version back to 5.2.0. Do it now, note why in the config, and tell Dana. This stops any more phones from being blocked. Do not wait on Apple: a review can take a day or 2, and this one setting removes the need for it.
What this does not fix: phones that already fetched 5.4.0 keep it until their hour is up. A phone that fetched at 09:12 can fetch again from 10:12. One that fetched right before your change, at about 09:42, must wait until about 10:42. So iPhone customers come back gradually, and all of them can be in by about 10:45 once they reopen the app. If the "Update required" page does not fetch again by itself, reopening is what triggers it. If your app applies a fetched value only at its next launch, it takes one more reopen.
Give support this line now, for the 190 open tickets too: "No update is needed. Close the app and reopen it after 10:45. If you still see the update page, reopen the app once more." Put it on your status page too. Reinstalling clears the kept value, but it is a full download and can sign the customer out, so offer it only to someone who cannot wait.
Then ask Dana what else assumed the 5.4.0 minimum. Any server change planned for today that drops support for older apps has to wait.
Read the signals. iOS sessions began to fall 3 minutes after the 09:12 change. API errors and latency are flat because a blocked app stops calling the API. The store shows why iPhones are stuck: 5.3.1 is the newest they can install, and it is below 5.4.0, so every iPhone that fetches the new minimum is blocked, with nothing to install.
They are still falling because each phone picks up the new value only when its hour is up. Left alone, every phone that opens the app would be blocked by about 10:12.
Android shares the setting, so Android phones below 5.4.0 were blocked too. Google Play has had 5.4.0 only since 08:30, so many Android phones were still below it at 09:12. They can update and come back. That explains a dip of about 10% with updates climbing. Putting the setting back frees them as well.
Other causes do not fit. A server fault would show in API errors. The App Store is not down either: App Store Connect shows 5.4.0 still waiting for review, so there is no update to find.
Confirm. Fetch the setting as an app does: it returns 5.2.0. Install 5.3.1 fresh on a test iPhone, so it holds no kept value: it opens normally. iOS sessions should start to climb within minutes and be near normal soon after 10:45, less anyone who gave up and ordered elsewhere.
Fix. Before this setting goes up again:
- That version must be live in that store, not only approved. An approved build still has to be released, and it can take time to appear.
- Most active phones on that platform must already run it. Apple's phased release spreads automatic updates over 7 days, so raising a minimum on release day is too soon on any platform.
- Keep one setting per platform, so an Android release cannot block iPhones.
- Make the config tool refuse a version above what the store has live, or require a second person to approve it.
Follow-ups.
- Have the "Update required" page fetch the setting again when it opens, so a mistake clears in minutes.
- Release 5.4.0 on iOS as normal once Apple approves it. It no longer depends on this setting.