Skip to content

Forcing Version Updates ​

The app can force engineers to update to a minimum version, or nudge them towards a recommended version. Both are controlled remotely via PostHog feature flags — no code changes or releases required.

How it works ​

Forced update ​

Shown when the engineer's app version is below min-app-version.

  • Title: "Update required"
  • Message: "This version of Zuno is no longer supported. Update to continue using the app and access new features."
  • Buttons: "Update now" (opens app store)
  • The back button is disabled — the engineer cannot dismiss this screen
  • The app is fully blocked until the engineer updates

Suggested update ​

Shown when the engineer's app version is below suggested-app-version but at or above min-app-version.

  • Title: "Update available"
  • Message: "A new version of Zuno is available with improvements and bug fixes. Update now to get the latest features."
  • Buttons: "Update now" (opens app store), "Update later" (dismisses for 24 hours)
  • The 24-hour dismissal survives app restarts — the engineer won't be prompted again until it expires

Safe defaults ​

When PostHog is unavailable, the flag is inactive, or the flag value is not a valid version string:

  • No update screens are shown — engineers can continue using the app normally
  • Invalid version values are reported to Sentry for investigation

How to force an update ​

Both min-app-version and suggested-app-version are multivariant flags in the Post-purchase PostHog project. The variant key is the version string.

To force or suggest an update to a new version:

  1. Open PostHog and switch to the Post-purchase [PROD] project
  2. Go to Feature Flags and find the flag (e.g. suggested-app-version)
  3. Under Variants, update the variant key to the new version (e.g. 3.1.0)
  4. Save the flag
  5. Ensure the flag is active (toggle on) — inactive flags won't trigger any update prompts

Be careful with min-app-version

Setting min-app-version higher than the latest version available in the app stores will lock all engineers out of the app with no way to update. Always verify the version exists in both the App Store and Google Play before activating this flag.

When to update each flag

  • suggested-app-version — update to the latest stable version roughly 1 week after a store release, once you're confident the release is stable.
  • min-app-version — update only when older versions must be blocked (e.g. breaking API changes, critical security fixes). This forces all engineers to update immediately.

Testing ​

In non-production builds, use the PostHog Flags tab in the debug drawer to override flag values without changing PostHog. Set the variant key to any version string to simulate forced or suggested update screens.