App update

The kit has two distinct update flows. Don't mix them up:

Both are native-only (they don't appear on web) and work in PT, EN, and ES across all three backends. The config comes from Firebase Remote Config, which is initialized in every project, even Supabase and API ones.

Implementation

Update available

1. In Firebase Remote Config, create two text keys:

   Key	Effect
   app_latest_version	The newest version in the store. If the user's version is lower → an optional notice (dismissible)
   app_min_version	The minimum accepted version. If the user's version is lower → a mandatory notice (blocks the app)

   Use SemVer (1.4.0). The default is 0.0.0: the feature stays off until you set a real value.

   

   An incorrect app_min_version locks out every user. Bump this value carefully.

2. Publish the version to the store, then bump app_latest_version afterward. The right flow is: publish to the store → go into Firebase Remote Config → bump app_latest_version (see why this is manual on purpose in Information).

   CLI shortcut, no need to open the console:

   # Interactive: suggests the version from pubspec, asks whether it's optional or mandatory
   kasy release-version
   
   # Direct
   kasy release-version -v 1.4.0
   
   # Mandatory, no prompts (good for CI)
   kasy release-version -v 1.4.0 -f --yes

   Via MCP: ask "mark version 1.4.0 as live in the stores" (set_release_version). For a blocking update, say it is mandatory (force). See Kasy MCP.

   The command reuses your firebase login, reads the project from google-services.json, and only updates the version keys, without overwriting the rest of Remote Config.

What's new

1. Update the version in pubspec.yaml (or use kasy ios release, which does it automatically):

   version: 1.2.0+5

2. Update the copy in lib/i18n/pt.i18n.json and lib/i18n/en.i18n.json:

   "update_bottom_sheet": {
     "title": "What's new?",
     "highlights": [
       "- New feature X added.",
       "- Performance improvements to the AI assistant.",
       "- Fixed a bug in social login."
     ]
   }

3. Regenerate the i18n files:

   dart run slang

   Done. On the user's next update, the sheet shows up automatically.

   Tracking is local (SharedPreferences). If the user installs on a new phone where the version is already the latest, the sheet doesn't show up: correct, since there was no update on that device.

Information

Why it's manual on purpose

The store takes time to approve. You might want a gradual rollout, or to only announce the update as optional after a few days. If the number were set automatically, you'd be telling people to "update" before the version was even available.

"Update" button

Takes the user straight to the store. On Android it works automatically. On iOS it needs the App Store ID: run kasy configure and fill in the App Store ID (numeric) field.

When "What's new" shows up

Last updated on 08/02/2026