A release should use your own infrastructure, identifiers, branding, and signing configuration. Complete this review before generating files for customers or app stores.

Configuration

1. Point Constants.baseUrl to your production HTTPS CRM.
2. Activate the correct API module license on that installation.
3. Replace sample Firebase configuration with your own project settings.
4. Verify your app name, icons, splash, translations, and contact information.
5. Confirm that privacy and terms content matches your actual service.

Build readiness

Set the release version/build number in pubspec.yaml. Keep the Android application ID and iOS bundle ID consistent with the existing store application when updating.

The inspected Android main manifest does not explicitly declare Internet permission. Verify the merged release manifest and ensure it contains this permission outside the application element:

The debug manifest alone is not sufficient evidence of production network access. Configure your own Android keystore and Apple signing team.

Customer checks

Test login, permissions, PDFs, ticket replies, and push delivery in release builds. Confirm that no demo records, test credentials, private keys, or verbose sensitive logs are included.

Prepare truthful store privacy disclosures and reviewer access to a test customer. Review any account-deletion or other store requirements applicable to your app’s features. Do not advertise unsupported payment, offline, or staff-management functionality.

Keep the exact source, dependency lockfile, signing details, and release test record for future maintenance.