Can we access your project?
Current Behavior
Clicking "Deploy" on the Push Notifications settings page always fails with: "Deployment Failed. Unknown error. Please contact support@flutterflow.io" (shown via the info icon next to "Not Deployed (Error)"). This happens on every attempt, regardless of settings.
Expected Behavior
Push Notifications should deploy successfully and show "Deployed" status, given that the Cloud Functions region matches (us-central1), all required IAM roles are present, and the project is on the Blaze plan with active billing.
Steps to Reproduce
Step 1: Open project Forge Faith (forge-by-faith-u1c1tx).
Step 2: Go to App Settings -> Push Notifications.
Step 3: Click "Deploy".
Step 4: Wait for the status to resolve (goes "In Progress" for < />20+ seconds, then fails).
Step 5: Click the info icon next to "Not Deployed (Error)" to see: "Deployment Failed. Unknown error. Please contact support@flutterflow.io".
Step 6: In Google Cloud Logging for this project, filter for protoPayload.methodName containing "Function" over the last 7 days: every deploy attempt shows successful GenerateUploadUrl calls (v1 us-central1, v2 us-central1, v2 us-east1), but there are zero CreateFunction or UpdateFunction calls logged afterward, ever - meaning the deploy process never reaches the actual function-creation step.
Reproducible from Blank
Bug Report Code (Required)
IT4wksmBw5F2pbxZ0a6JdPpVoGAUMjt+RIIwmuthRis9f5CvOpYUec/6PhFoUte9TGw7MWK2p14f0d7xvd/DK+4rFw2aQapZybl+ZQvwUn+Qb62TF7u/e39QBphNBVS15J2RhRQnWepZSHAF1E6mAtmRTXLdQ5DaIVQ8Sq/LZO4=
Visual documentation
(Automated upload of screenshots to this form was not possible in this session.) Key visual evidence: 1) The FlutterFlow Push Notifications page shows a modal titled "Deployment Failed" with body text "Unknown error. Please contact support@flutterflow.io" when clicking the info icon next to "Not Deployed (Error)". 2) Google Cloud Logging (Logs Explorer) for this project, filtered on protoPayload.methodName:"functions" over the last 7 days, shows repeated successful google.cloud.functions.v1.CloudFunctionsService.GenerateUploadUrl and google.cloud.functions.v2.FunctionService.GenerateUploadUrl audit log entries (in us-central1 and us-east1), each returning HTTP 200 with a valid upload_url in the response, but a separate query for protoPayload.methodName:("CreateFunction" OR "UpdateFunction") over the same 7-day window returns 0 results.
Environment
- FlutterFlow version: Web app, current as of 2026-07-28
- Platform: Web (FlutterFlow browser-based editor)
- Browser name and version: Chromium-based browser
- Operating system and version affected: N/A (issue is project/backend-side, not client-specific)
Additional Information
This blocks a daily reminder push notification feature we recently built for our users. Before filing this, we ruled out the two most common causes: (1) Cloud Functions region mismatch - confirmed Settings > Firebase > Advanced Settings region (us-central1) matches all 4 existing deployed functions (sendPushNotificationsTrigger, sendScheduledPushNotifications, onUserDeleted, addFcmToken), all in us-central1, no functions exist in any other region; (2) IAM permissions - confirmed via Google Cloud IAM that firebase@flutterflow.io has Editor, Cloud Functions Admin, and Service Account User, and the project's FlutterFlow-managed service account has even broader roles. We also confirmed the project is on the Blaze plan with active billing, and that toggling "Allow Scheduling" off and redeploying fails identically, ruling out our specific reminder-scheduling configuration as the cause. This points to a bug in FlutterFlow's own deployment pipeline for this project that stops progressing after the GenerateUploadUrl step. There are 3 potential duplicate issues flagged by GitHub (#7319, #7318, #6830) that may be related - #7318 in particular ("Push Notifications deployment fails before Cloud Build with HTTP 409") was marked "can't reproduce," but we're providing concrete audit-log evidence here that should help reproduce and diagnose it this time.
Can we access your project?
Current Behavior
Clicking "Deploy" on the Push Notifications settings page always fails with: "Deployment Failed. Unknown error. Please contact support@flutterflow.io" (shown via the info icon next to "Not Deployed (Error)"). This happens on every attempt, regardless of settings.
Expected Behavior
Push Notifications should deploy successfully and show "Deployed" status, given that the Cloud Functions region matches (us-central1), all required IAM roles are present, and the project is on the Blaze plan with active billing.
Steps to Reproduce
Step 1: Open project Forge Faith (forge-by-faith-u1c1tx).
Step 2: Go to App Settings -> Push Notifications.
Step 3: Click "Deploy".
Step 4: Wait for the status to resolve (goes "In Progress" for < />20+ seconds, then fails).
Step 5: Click the info icon next to "Not Deployed (Error)" to see: "Deployment Failed. Unknown error. Please contact support@flutterflow.io".
Step 6: In Google Cloud Logging for this project, filter for protoPayload.methodName containing "Function" over the last 7 days: every deploy attempt shows successful GenerateUploadUrl calls (v1 us-central1, v2 us-central1, v2 us-east1), but there are zero CreateFunction or UpdateFunction calls logged afterward, ever - meaning the deploy process never reaches the actual function-creation step.
Reproducible from Blank
Bug Report Code (Required)
IT4wksmBw5F2pbxZ0a6JdPpVoGAUMjt+RIIwmuthRis9f5CvOpYUec/6PhFoUte9TGw7MWK2p14f0d7xvd/DK+4rFw2aQapZybl+ZQvwUn+Qb62TF7u/e39QBphNBVS15J2RhRQnWepZSHAF1E6mAtmRTXLdQ5DaIVQ8Sq/LZO4=
Visual documentation
(Automated upload of screenshots to this form was not possible in this session.) Key visual evidence: 1) The FlutterFlow Push Notifications page shows a modal titled "Deployment Failed" with body text "Unknown error. Please contact support@flutterflow.io" when clicking the info icon next to "Not Deployed (Error)". 2) Google Cloud Logging (Logs Explorer) for this project, filtered on protoPayload.methodName:"functions" over the last 7 days, shows repeated successful google.cloud.functions.v1.CloudFunctionsService.GenerateUploadUrl and google.cloud.functions.v2.FunctionService.GenerateUploadUrl audit log entries (in us-central1 and us-east1), each returning HTTP 200 with a valid upload_url in the response, but a separate query for protoPayload.methodName:("CreateFunction" OR "UpdateFunction") over the same 7-day window returns 0 results.
Environment
Additional Information
This blocks a daily reminder push notification feature we recently built for our users. Before filing this, we ruled out the two most common causes: (1) Cloud Functions region mismatch - confirmed Settings > Firebase > Advanced Settings region (us-central1) matches all 4 existing deployed functions (sendPushNotificationsTrigger, sendScheduledPushNotifications, onUserDeleted, addFcmToken), all in us-central1, no functions exist in any other region; (2) IAM permissions - confirmed via Google Cloud IAM that firebase@flutterflow.io has Editor, Cloud Functions Admin, and Service Account User, and the project's FlutterFlow-managed service account has even broader roles. We also confirmed the project is on the Blaze plan with active billing, and that toggling "Allow Scheduling" off and redeploying fails identically, ruling out our specific reminder-scheduling configuration as the cause. This points to a bug in FlutterFlow's own deployment pipeline for this project that stops progressing after the GenerateUploadUrl step. There are 3 potential duplicate issues flagged by GitHub (#7319, #7318, #6830) that may be related - #7318 in particular ("Push Notifications deployment fails before Cloud Build with HTTP 409") was marked "can't reproduce," but we're providing concrete audit-log evidence here that should help reproduce and diagnose it this time.