Push Notifications report Deployed but addFcmToken is not created

[business853]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Project: BEFORE
Project ID: before-jm3x4r

Push Notifications are enabled, but the Android app cannot register an FCM device token and manual notifications report Sent to 0 devices.

We followed FlutterFlow’s documented troubleshooting for this issue:

Firebase project is on Blaze.
Firebase Cloud Messaging API is enabled.
Cloud Functions region is us-central1.
firebase@flutterflow.io has Editor, Cloud Functions Admin, and Service Account User.
Android notification permission is enabled.
Existing addFcmToken was manually deleted as instructed in FlutterFlow’s “Sent to 0 Devices” troubleshooting.
FlutterFlow then changed to Not Deployed and displayed the Deploy button.
Deploy was run successfully and FlutterFlow returned to Deployed.

However, after deployment:

addFcmToken was not recreated in Google Cloud Functions (1st Gen).
sendScheduledPushNotifications is present.
Cloud Run contains sendpushnotificationstrigger and senduserpushnotificationstrigger.
Google Cloud Logs searched for addFcmToken show only the DeleteFunction events from September 13, 2026.
There are no subsequent CreateFunction or UpdateFunction events for addFcmToken.
Searching activity from the FlutterFlow service account during the redeployment window yielded no results.
The user document therefore has no fcm_token subcollection, and FlutterFlow continues to report 0 devices.

Please investigate why Push Notification deployment reports Deployed while the required addFcmToken function is not being created, and restore/redeploy that managed function for this project.

Expected Behavior

Expected Result:
FlutterFlow deployment should recreate addFcmToken, allow the Android device to register its FCM token, and make the device available for push notification delivery.

Actual Result:
FlutterFlow reports Deployed, but addFcmToken is not recreated, no FCM token is registered, and notifications report Sent to 0 devices.

Steps to Reproduce

Open project BEFORE in FlutterFlow.
Go to App Settings → Push Notifications.
Confirm:
Enable Push Notifications = ON
Allow Scheduling = ON
Automatically Prompt Users for Permission = ON
Deployment Status = Deployed
In Google Cloud Functions, confirm addFcmToken is not present.
Following FlutterFlow troubleshooting, delete the existing addFcmToken function if present.
Return to FlutterFlow Push Notifications.
Toggle Push Notifications OFF and back ON so FlutterFlow recognizes the missing deployment.
FlutterFlow changes to Not Deployed and shows Deploy.
Click Deploy.
FlutterFlow completes deployment and returns to Deployed.
Return to Google Cloud Functions → Functions (1st Gen) and refresh.
sendScheduledPushNotifications is present, but addFcmToken is not recreated.
In Logs Explorer, search for addFcmToken. The only recent entries are DeleteFunction; there are no subsequent CreateFunction or UpdateFunction events.
Install/open the Android app with notifications allowed and sign in.
FlutterFlow manual push notification test reports Sent to 0 devices because no FCM token is registered.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITFXlvHl04lPm9hE1ZCIY8ZGnikwGW4La+dI0tZ+TQ0jF5D4B+x/esnRQFJuZ9OrY1c2fE6cp14B+cr8jtnuUvUrB0yWQKE5+M9pEzzKYEitbrmTF7uae3wnBcNYN2ay4Z+JvRJNNthYWkYZ7U6EAvKtXijfJ4P6IFQ8Sq/LZO4=

Visual documentation

Environment

- FlutterFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information