> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/native-integrations/overview-1/force-app-update.md).

# Force App Update

Require users to update when you ship a key release.

Force App Update asks customers on an older version of your app to update before they carry on.

Most of your changes reach customers over the air without any update at all — see [Publish Changes to Production](https://help.twinr.dev/app-version/publish-changes-to-production.md). This is for the occasions when a change needs the new build itself: a fixed payment flow, a security patch, a feature the old version cannot run.

## Turn it on

Open **Native Features → Force App Update** and switch on **Enable Force App Update**.

<figure><img src="https://3731994945-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlBy5z08zL1UoCwNqmg%2Fuploads%2Fgit-blob-d006781b5d0600bee7198d830cfa18a7cf2e0e90%2Fnf-force-app-update.png?alt=media" alt="The Force App Update screen with its enable toggle and Customization tab"><figcaption></figcaption></figure>

The settings below the toggle stay hidden until it is on. The **Customization** tab controls how the prompt looks and what it says.

Click **Save as draft**.

## Use it sparingly

A forced update interrupts someone who opened your app to do something. They did not plan to visit an app store, and some will close the app instead of updating.

Worth forcing: a broken checkout, a security fix, a version so old it no longer works with your site.

Not worth forcing: a redesign, a new feature, anything you simply want people on. Those arrive on their own as customers update normally.

{% hint style="warning" %}
Only turn this on once the new version is **live in both stores**. If you force an update to a build Apple is still reviewing, customers are sent to a store page that does not offer it yet — and they cannot get past the prompt. Check both stores before publishing this change.
{% endhint %}

## Check it

Because the prompt only appears to customers on an older version, the safest check is in Twinr Preview with the prompt enabled, confirming the wording reads well and the store link opens the right listing. See [Preview App](https://help.twinr.dev/create-app/preview-app.md).
