Before running, configure your CRM URL and Android Firebase application. Use the package name that matches your Firebase registration.
For a physical device, enable developer options and USB debugging, connect it to your computer, and accept the device’s debugging authorization prompt. Alternatively, start an Android emulator. Use an emulator image with the services required for Firebase messaging when testing push delivery.
From the Flutter project root:
Replace DEVICE_ID with the ID reported by flutter devices.
Complete onboarding, sign in with your test customer contact, and open an allowed feature. Test over the same network conditions your customers will use. Accept notification permission if you want to test push messages.
Changing Dart widgets usually allows a hot reload during development. Changes to Firebase files, the Android manifest, Gradle, or application identifiers need a new build and restart.
A debug run does not validate a production build. In particular, inspect network permission in the release manifest and configure your own release signing key before generating an APK or AAB.
If the device is not detected, fix USB authorization, drivers, or emulator setup before troubleshooting the CRM API. If it starts but cannot connect, use App Cannot Connect to Perfex CRM.