Firebase Setup Stuck: "Reconnect Failed" (Organization Policy) even after fixing GCP and adding manual Editor role

[NathanGermano]

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

My Firebase connection is stuck on the "Reconnect Failed: Unable to provision the FlutterFlow service account in your project. There may be an organization policy preventing service-account creation." error.

What I have tried (and didn't work):

I am using a GCP project under an Organization, which had the iam.disableServiceAccountCreation policy active.

I went to Google Cloud Console and completely disabled/overridden this policy.

I went to Firebase IAM and manually added firebase@flutterflow.io with the "Editor" role.

Inside FlutterFlow, I clicked "Remove" on the Firebase Project ID, refreshed the page (F5), and re-entered the ID.

Even with the permissions fully granted and the service account already present in Firebase, FlutterFlow is stuck in a cache loop showing the exact same red error box. It prevents me from regenerating the config files.

Please help force-reset this connection state.

Firebase account: sinucaja@gmail.com

Expected Behavior

FlutterFlow should verify the connection and show "Firebase Setup Complete!" so I can regenerate my config files. Since I already manually assigned the "Editor" role to firebase@flutterflow.io in my Firebase project, the system should recognize the existing permissions instead of trying to create a new service account and getting stuck on the cached policy error.

Steps to Reproduce

1. Start with a Firebase project connected to a Google Cloud Organization that has the iam.disableServiceAccountCreation policy enabled.

2. In FlutterFlow (App Settings > Firebase), enter the Firebase Project ID and try to connect.

3. Receive the "Reconnect Failed" error regarding the organization policy.

Go to Google Cloud Console and completely disable/override the iam.disableServiceAccountCreation policy for the project.

4. Go to Firebase Console (Users and Permissions) and manually add firebase@flutterflow.io as an Editor.

5. Return to FlutterFlow, click "Remove" on the Firebase setup, refresh the page, and try to connect the Project ID again.

6. Notice that FlutterFlow is stuck in a loop, showing the exact same policy error and ignoring the manually added permissions.

Reproducible from Blank

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

Bug Report Code (Required)

IT4wiMjfsI52rt9G+KX2acFsmjosIjs1R5IF0upxRis8GZT0B4kcYs+kfklUOMDgSlZUfWCaknwX/MrTj4fLJMdfKSiCbYhEyahcSQLhTlGnR7ayO5S3b3x8EeZWBWqj0Z6RuiZ4Iu51LVIE707yNd+UYCbYJIDxIkYgR+aoXdeK2SrDX1iXc2URm05KZDPz

Visual documentation

Environment

FlutterFlow version: Latest Web Version

Platform: Web

Browser name and version: Google Chrome (Latest)

Operating system and version affected: Windows 11

Additional Information

No response

[br0nk]

Please try additionally lifting iam.disableServiceAccountKeyCreation for that project in your org policies. This should be doable in the Google Cloud Console in: IAM & Admin → Organization Policies → search "Disable service account key creation" → Manage policy → add a rule scoped to project projetosinuca-a8f73 → set Not enforced / Off → Save.