How to Troubleshoot Common FlutterFlow Push Notification Problems

If push notifications work on Android but not on iOS, the APNs key is almost certainly missing or wrong. Go to Apple Developer Portal > Certificates, Identifiers & Profiles > Keys. Create a new key with 'Apple Push Notifications service (APNs)' checked. Download the .p8 file — it can only be downloaded once. Note the Key ID and your Team ID (shown in the upper right of the Apple Developer portal). In Firebase Console > Project Settings > Cloud Messaging > Apple app configuration, upload the .p8 file and enter the Key ID and Team ID. This single key works for both development and production APNs environments, unlike the older certificate approach.

If your FlutterFlow app calls the get FCM token action and gets back a null or empty value, the first reaction is usually to check the code. Stop. A null FCM token on iOS almost always means the user has not granted notification permission — either they tapped 'Don't Allow' on the permission prompt, or you never showed the prompt. On Android 13+, the same applies. In FlutterFlow check whether you have a Request Notification Permission action before you try to get the FCM token. Add a Custom Action that checks FirebaseMessaging.instance.getNotificationSettings() and reads the authorizationStatus. If it returns denied or notDetermined, show a dialog explaining why notifications are useful before calling requestPermission.

1// Custom Action: checkNotificationPermission.dart
2import 'package:firebase_messaging/firebase_messaging.dart';
3
4Future<String> checkNotificationPermission() async {
5  final settings =
6      await FirebaseMessaging.instance.getNotificationSettings();
7  switch (settings.authorizationStatus) {
8    case AuthorizationStatus.authorized:
9      return 'authorized';
10    case AuthorizationStatus.denied:
11      return 'denied';
12    case AuthorizationStatus.notDetermined:
13      return 'not_determined';
14    case AuthorizationStatus.provisional:
15      return 'provisional';
16    default:
17      return 'unknown';
18  }
19}

By default on iOS, notifications received while your app is in the foreground are silently dropped — they do not appear as banners or sounds. This is an Apple system behavior. On Android, foreground notifications are delivered but the visual presentation depends on your notification channel setup. In FlutterFlow add a Custom Action called setupForegroundHandler that calls FirebaseMessaging.instance.onMessage.listen. Inside the listener, use the flutter_local_notifications package to display a local notification when an FCM message arrives while the app is open. Register this handler in your app's initialization flow so it is active throughout the app's lifetime.

1// Custom Action: setupForegroundHandler.dart
2import 'package:firebase_messaging/firebase_messaging.dart';
3import 'package:flutter_local_notifications/flutter_local_notifications.dart';
4
5final _localNotifications = FlutterLocalNotificationsPlugin();
6
7Future setupForegroundHandler() async {
8  // Initialize local notifications
9  const initSettings = InitializationSettings(
10    android: AndroidInitializationSettings('@mipmap/ic_launcher'),
11    iOS: DarwinInitializationSettings(),
12  );
13  await _localNotifications.initialize(initSettings);
14
15  // Listen for foreground FCM messages
16  FirebaseMessaging.onMessage.listen((RemoteMessage message) async {
17    if (message.notification != null) {
18      await _localNotifications.show(
19        message.hashCode,
20        message.notification!.title,
21        message.notification!.body,
22        const NotificationDetails(
23          android: AndroidNotificationDetails(
24            'default_channel', 'Default',
25            importance: Importance.high,
26            priority: Priority.high,
27          ),
28          iOS: DarwinNotificationDetails(),
29        ),
30      );
31    }
32  });
33}

A common scenario: push notifications work perfectly in development but fail silently in the App Store or Google Play build. The cause is a Firebase project mismatch. FlutterFlow connects to one Firebase project, but if you downloaded your app code and built it locally, or used a different google-services.json, it may point to a different project. Check: in FlutterFlow Settings > Firebase > Firebase Project, note your project ID. On your deployed device, the FCM token is registered to the Firebase project embedded in the app's google-services.json (Android) or GoogleService-Info.plist (iOS). If you send a notification from the wrong Firebase project, the token does not exist in that project and the message fails silently. Always send test notifications from the same Firebase Console project that matches your app bundle.

Before debugging your FlutterFlow code, eliminate the delivery infrastructure as the cause. In Firebase Console > Cloud Messaging, click 'Send your first message' or 'New notification'. Write a test title and body, click 'Send test message', and paste your device's FCM token (from your app's debug output or a Custom Action that logs the token). If this test succeeds, FCM delivery works and the problem is in your FlutterFlow action that triggers the notification. If it fails, the problem is in your Firebase project configuration (APNs key, token registration). This binary test saves hours of debugging the wrong layer.