Register an iOS app in Firebase using the Runner target’s exact bundle identifier. Use your own Apple development team and Firebase project.
Download GoogleService-Info.plist from the matching Firebase iOS registration. Add it to the Runner project in Xcode and verify Runner target membership. Run FlutterFire configuration and check the generated iOS options.
Enable Push Notifications for the Runner target. Configure the required Background Modes options, including remote notifications, and ensure your provisioning supports the enabled capabilities. Upload an APNs authentication key and its identifiers in Firebase’s Cloud Messaging settings, following the FCM Flutter instructions.
Keep the APNs private key outside the app source and distribution archive.
Build on a Mac, install on a test iPhone, allow notifications, and sign in with a customer contact. Send a test push through the CRM module. Check the application both while open and while in the background.
If delivery fails, compare the bundle identifier across Xcode, Firebase, and Apple signing configuration. Check that an APNs token becomes available before diagnosing FCM token registration.
The supplied repository still needs a complete iOS release validation for your identifiers, signing team, Firebase configuration, and selected native dependencies. Configuration files alone do not establish successful APNs delivery.