🚨 [BUG] Persistent Error: "Could not create an account as firebase@flutterflow.io" in Data Manager

Hello Everyone 👋

Thank you all in advance for your help 🙏

I am unable to use "Manage Content" for any collection (e.g., signals). The connection is blocked by a persistent service account creation error.

Despite verifying and resetting every standard configuration, this error will not clear.

🛑 The Error Message

When clicking the Manage Content button in the Firestore Data Manager, I repeatedly receive this error:"Could not create an account as [email protected] to your Firebase project. Make sure 'Email Sign-In' is turned on for your Firebase project, and try again."

❓ Request for Help

Since every step governing user creation and authentication has been verified as correct, the service is clearly failing at a deeper level than the standard configurations account for.

Has anyone in the community successfully resolved this persistent error after exhausting the above steps? I am looking for a non-standard fix (e.g., an obscure GCP API key setting or a known workaround).

Thank you for your time and help!

✅ Troubleshooting Steps Completed

I have verified all external settings and performed all suggested internal resets.

I. Firebase Authentication & User Management

• Email/Password Sign-In: Confirmed Enabled under Authentication \rightarrow Sign-in method.

• User Creation Enabled: Confirmed "Enable create (sign-up)" is checked under Authentication \rightarrow Settings \rightarrow User actions.

• Service User Exists: The user [email protected] has been manually created (or exists) and is visible in Firebase \rightarrow Project Settings \rightarrow Users and permissions.

II. FlutterFlow Connection Reset & Config

• Project Connection Status: Currently shows "Firebase Setup Complete!" in App Settings.

• Disconnect/Reconnect: The project was completely removed and reconnected.

• Config Regeneration: I clicked "Regenerate Config Files" in the Firebase settings.

III. Firebase IAM Permissions

I have manually verified and granted the [email protected] service account the following roles in Google Cloud IAM:

• Editor (Broad access, confirmed in IAM dashboard).

• Cloud Functions Admin.

• Service Account User.

• Firebase Authentication Admin (Explicit permission to manage users).

IV. Security Rules (Verified for Service User)

My Firestore Security Rules have been configured to explicitly allow read/write access for the service user:

🚨 [BUG] Persistent Error: "Could not create an account as [email protected]" in Data Manager