An APK is useful for installing a signed Android build directly on a test device or distributing through a permitted channel outside the store workflow.
Complete Preparing Flutex for Production and How to Sign Your Android App. Verify the CRM URL, Firebase configuration, Internet permission, and version number.
From the project root, run:
The usual output is build/app/outputs/flutter-apk/app-release.apk. For smaller architecture-specific packages, use flutter build apk --release --split-per-abi and distribute the APK appropriate for the device. See Flutter’s Android build guide.
Install the generated APK on a test device. Verify startup, customer login, record loading, PDF viewing, and notifications. Do not rely on a previous flutter run session as proof that this APK works.
An update must use a compatible application identity and signing certificate. If Android rejects installation, capture its exact error before deleting the existing app. Uninstalling can remove local app data and conceal a signing mismatch that would also affect your customers.
Keep the signed artifact with its version, build number, and source revision. Never distribute your keystore or key.properties alongside the APK.