Update the mobile app and API module as a compatible release pair. Review the supplied release notes before applying files to production.
Download the new release from your purchase account. Back up the current mobile source, CRM database, server files, uploads, and environment settings. Preserve signing keys and Firebase/server credentials separately and securely.
Compare the release notes with your current app, API, Perfex, PHP, and Flutter versions. Check for migrations or changed request/response behavior.
Install the updated module using the release’s instructions and merge mobile customizations into the new source. Restore your CRM URL, branding, Firebase configuration, and established application identifiers without copying obsolete integration code over the update.
Run the installation verification checklist. Include login/refresh, permissions, PDFs, customer mutations, and push delivery.
Follow any documented backend/mobile deployment order. Existing customer app versions may remain installed after you publish a new release, so confirm their compatibility with the updated module or plan the transition explicitly.
Increase the mobile build number, sign with the established credentials, and distribute through your normal release channel. Monitor server errors and customer reports.
If rollback is necessary, restore a compatible application/database/module set. Do not assume copying old PHP files over a migrated database is a safe rollback procedure.