Can we access your project?
Current Behavior
My FlutterFlow project is unable to complete deployment of the automatically generated deleteUserReference Cloud Function.
The project is already connected to Firebase and is on the Firebase Blaze (pay-as-you-go) plan.
The problem started while configuring Firestore permissions and the deleteUserReference function used by FlutterFlow for deleting user references/data.
FlutterFlow repeatedly instructed me to “Deploy Firestore rules first”, even though the Firestore rules had already been deployed. We reviewed and corrected the Firestore collection permissions/rules and successfully deployed the Firestore rules again, but the Cloud Function still would not deploy normally.
We also encountered schema validation/deployment failures, including a cloud_firestore/permission-denied error during validation.
The deleteUserReference deployment has also appeared to remain stuck/processing from a previous deployment attempt. Repeated deployment attempts from FlutterFlow have not resolved the condition.
Troubleshooting already completed:
● Confirmed Firebase project is on the Blaze plan.
● Confirmed FlutterFlow is connected to the correct Firebase project.
● Reviewed Firestore collections and their permissions/rules.
● Corrected Firestore rule warnings that were identified.
● Successfully redeployed Firestore rules.
● Reviewed Firestore indexes/deployment status.
● Retried deleteUserReference deployment multiple times.
● Retried FlutterFlow schema validation.
● Reviewed the deployment/function status in Google Cloud.
● Reviewed Google Cloud IAM permissions for the project.
● Added/verified required IAM roles, including Editor, Service Account User, and the Cloud Functions/Cloud Run-related permissions required during troubleshooting.
● Reviewed Cloud Run after FlutterFlow directed us there to manage the function.
● Updated the function runtime to Node.js 20 when required.
● A deployment operation completed after the Node.js/runtime work, but FlutterFlow continued to report/block the function deployment.
● Logged out and back into FlutterFlow.
● Cleared browser/cache and retried.
● Tested in an incognito/private browser session.
● Repeated deployment after these steps.
The FlutterFlow application itself continues to run in Test Mode, and Firestore data is being retrieved by the application. This does not appear to be a general Firebase connection failure.
At this point, the issue appears specifically related to FlutterFlow’s Firestore schema validation / generated deleteUserReference deployment workflow rather than the application UI or normal Firestore reads.
Because multiple deployment attempts and the recommended Firebase/Google Cloud permission changes have already been performed, I would appreciate if the FlutterFlow team could inspect the project and determine why FlutterFlow continues to block or fail deployment of deleteUserReference.
Expected Behavior
After Firestore rules are successfully deployed and the Firebase project is correctly configured on the Blaze plan with the required Google Cloud permissions, FlutterFlow should successfully validate the Firestore schema and deploy the generated deleteUserReference Cloud Function.
FlutterFlow should not continue requesting that Firestore rules be deployed when those rules have already been successfully deployed, and the function should not remain stuck/not deployed after a successful deployment operation.
Steps to Reproduce
- Open the existing FlutterFlow project connected to Firebase.
2. Confirm that the Firebase project is on the Blaze plan.
3. Confirm that Firestore rules have already been successfully deployed in Firebase.
4. Open FlutterFlow > Firebase/Firestore settings.
5. Attempt to deploy the deleteUserReference Cloud Function.
6. FlutterFlow continues to indicate that Firestore rules must be deployed first, even though the rules are already deployed.
7. Attempt the Firestore rules deployment again from FlutterFlow.
8. The deployment does not resolve the condition and the Cloud Function remains blocked/not deployable.
9. Refresh FlutterFlow, sign out and back in, clear browser cache, and retry deployment.
10. Confirm in Google Cloud/Firebase that the required IAM roles and services are configured and that the project remains on the Blaze plan.
11. Retry deployment of deleteUserReference.
12. Observe that the same deployment block persists and FlutterFlow still does not allow the function to deploy.
Reproducible from Blank
Bug Report Code (Required)
IT4KifLqx49Pj7xa1s76LO9ViicWHGY8RIE8ltVtRQ82CLL2G7YMS8+kMxJVXemndGNEL0yJuz8d+tGNvc7+A+UnBwyCGK5byqtUTAHJeGOtVKanBpCzOWskN/FJJVyc36u3sCZRKrZiZVEs1GWEJ++QaBfAHZzvOzBEHuSXDJrDs2upQ0SLb3kNh1JWeC/v
Visual documentation
Screenshots attached showing FlutterFlow repeatedly requesting Firestore rules deployment even though the rules have already been successfully deployed in Firebase, and showing the deleteUserReference Cloud Function remaining stuck/not deployable.
This is a project-level backend deployment issue, not a widget-specific issue. The Bug Report Code above was generated from an arbitrary widget only because the form requires one.
Environment
● Platform: FlutterFlow Web
● Device: MacBook
● Operating System: macOS Tahoe 26.5.2
● Browser: Google Chrome- Version 151.0.7922.140
● Backend: Firebase / Google Cloud
● Firebase Billing Plan: Blaze
● Database: Cloud Firestore
● Cloud Function affected: deleteUserReference
● Cloud Functions runtime: Node.js 20
● Issue type: Firestore Rules / Cloud Function deployment
● FlutterFlow version: Current web version as of August 22, 2026
Additional Information
This issue is currently blocking the release of my application, Oasis.
The application itself is substantially complete and functional in testing, but I cannot proceed with the final production/release process while FlutterFlow is unable to successfully complete the Firestore/schema validation and deploy the deleteUserReference Cloud Function.
I have spent several days troubleshooting this issue and have already completed the recommended Firebase, Firestore, Google Cloud IAM, Cloud Functions/Cloud Run, Node.js runtime, browser/cache, and deployment troubleshooting steps described above. The Firebase project is also confirmed to be on the Blaze plan.
At this point, further application development and release preparation are being delayed specifically by this deployment problem.
I would greatly appreciate FlutterFlow engineering reviewing the project directly, since repeated deployment attempts and configuration changes have not resolved the issue. This is a production release blocker for Oasis.
Can we access your project?
Current Behavior
My FlutterFlow project is unable to complete deployment of the automatically generated deleteUserReference Cloud Function.
The project is already connected to Firebase and is on the Firebase Blaze (pay-as-you-go) plan.
The problem started while configuring Firestore permissions and the deleteUserReference function used by FlutterFlow for deleting user references/data.
FlutterFlow repeatedly instructed me to “Deploy Firestore rules first”, even though the Firestore rules had already been deployed. We reviewed and corrected the Firestore collection permissions/rules and successfully deployed the Firestore rules again, but the Cloud Function still would not deploy normally.
We also encountered schema validation/deployment failures, including a cloud_firestore/permission-denied error during validation.
The deleteUserReference deployment has also appeared to remain stuck/processing from a previous deployment attempt. Repeated deployment attempts from FlutterFlow have not resolved the condition.
Troubleshooting already completed:
● Confirmed Firebase project is on the Blaze plan.
● Confirmed FlutterFlow is connected to the correct Firebase project.
● Reviewed Firestore collections and their permissions/rules.
● Corrected Firestore rule warnings that were identified.
● Successfully redeployed Firestore rules.
● Reviewed Firestore indexes/deployment status.
● Retried deleteUserReference deployment multiple times.
● Retried FlutterFlow schema validation.
● Reviewed the deployment/function status in Google Cloud.
● Reviewed Google Cloud IAM permissions for the project.
● Added/verified required IAM roles, including Editor, Service Account User, and the Cloud Functions/Cloud Run-related permissions required during troubleshooting.
● Reviewed Cloud Run after FlutterFlow directed us there to manage the function.
● Updated the function runtime to Node.js 20 when required.
● A deployment operation completed after the Node.js/runtime work, but FlutterFlow continued to report/block the function deployment.
● Logged out and back into FlutterFlow.
● Cleared browser/cache and retried.
● Tested in an incognito/private browser session.
● Repeated deployment after these steps.
The FlutterFlow application itself continues to run in Test Mode, and Firestore data is being retrieved by the application. This does not appear to be a general Firebase connection failure.
At this point, the issue appears specifically related to FlutterFlow’s Firestore schema validation / generated deleteUserReference deployment workflow rather than the application UI or normal Firestore reads.
Because multiple deployment attempts and the recommended Firebase/Google Cloud permission changes have already been performed, I would appreciate if the FlutterFlow team could inspect the project and determine why FlutterFlow continues to block or fail deployment of deleteUserReference.
Expected Behavior
After Firestore rules are successfully deployed and the Firebase project is correctly configured on the Blaze plan with the required Google Cloud permissions, FlutterFlow should successfully validate the Firestore schema and deploy the generated deleteUserReference Cloud Function.
FlutterFlow should not continue requesting that Firestore rules be deployed when those rules have already been successfully deployed, and the function should not remain stuck/not deployed after a successful deployment operation.
Steps to Reproduce
2. Confirm that the Firebase project is on the Blaze plan.
3. Confirm that Firestore rules have already been successfully deployed in Firebase.
4. Open FlutterFlow > Firebase/Firestore settings.
5. Attempt to deploy the deleteUserReference Cloud Function.
6. FlutterFlow continues to indicate that Firestore rules must be deployed first, even though the rules are already deployed.
7. Attempt the Firestore rules deployment again from FlutterFlow.
8. The deployment does not resolve the condition and the Cloud Function remains blocked/not deployable.
9. Refresh FlutterFlow, sign out and back in, clear browser cache, and retry deployment.
10. Confirm in Google Cloud/Firebase that the required IAM roles and services are configured and that the project remains on the Blaze plan.
11. Retry deployment of deleteUserReference.
12. Observe that the same deployment block persists and FlutterFlow still does not allow the function to deploy.
Reproducible from Blank
Bug Report Code (Required)
IT4KifLqx49Pj7xa1s76LO9ViicWHGY8RIE8ltVtRQ82CLL2G7YMS8+kMxJVXemndGNEL0yJuz8d+tGNvc7+A+UnBwyCGK5byqtUTAHJeGOtVKanBpCzOWskN/FJJVyc36u3sCZRKrZiZVEs1GWEJ++QaBfAHZzvOzBEHuSXDJrDs2upQ0SLb3kNh1JWeC/v
Visual documentation
Screenshots attached showing FlutterFlow repeatedly requesting Firestore rules deployment even though the rules have already been successfully deployed in Firebase, and showing the deleteUserReference Cloud Function remaining stuck/not deployable.
This is a project-level backend deployment issue, not a widget-specific issue. The Bug Report Code above was generated from an arbitrary widget only because the form requires one.
Environment
Additional Information
This issue is currently blocking the release of my application, Oasis.
The application itself is substantially complete and functional in testing, but I cannot proceed with the final production/release process while FlutterFlow is unable to successfully complete the Firestore/schema validation and deploy the deleteUserReference Cloud Function.
I have spent several days troubleshooting this issue and have already completed the recommended Firebase, Firestore, Google Cloud IAM, Cloud Functions/Cloud Run, Node.js runtime, browser/cache, and deployment troubleshooting steps described above. The Firebase project is also confirmed to be on the Blaze plan.
At this point, further application development and release preparation are being delayed specifically by this deployment problem.
I would greatly appreciate FlutterFlow engineering reviewing the project directly, since repeated deployment attempts and configuration changes have not resolved the issue. This is a production release blocker for Oasis.