App status and force-update

FrappeAppGuard calls mobile_auth.app_status on every app launch. This is how a server-side change reaches every installed app without a code release.

What it checks

• Enabled. If Mobile Configuration.enabled is off, or the endpoint is missing entirely, the app is blocked.
• Version. If the installed app version is below minimum_app_version, the guard shows a force-update screen and redirects to the store.
• Package name. If the app's package name does not match package_name on Mobile Configuration, the guard treats it the same as a version mismatch.
• Maintenance mode. If maintenance_mode is on, the guard shows maintenance_message instead of the app.

Force-update screen

Triggered by either a version below the floor or a package name mismatch. It redirects the user to the Play Store or App Store rather than letting them continue with a build the server no longer supports.

Blocking the app

enabled == false or a missing/failing app_status call blocks the app outright. Use this to kill a deployment without touching the app store listing.

Where the flag comes from

Everything the guard checks lives on Mobile Configuration. See Configuration for the full field set.