FlutterFlow is retiring legacy Firebase access (the firebase@flutterflow.io identity) in stages. If your project still connects to Firebase through legacy access, reconnect it with Google as soon as possible.
Legacy access shutdown dates
Date | What changes |
October 14, 2026 | You can't create new legacy connections. A "Legacy Firebase Access" entry appears in Project Issues for projects that still use legacy access. Deploys keep working. |
October 28, 2026 | Deploys from projects that still use legacy access fail, unless support granted the project emergency access. |
November 30, 2026 | Emergency access ends. Deploys from projects that still use legacy access fail for everyone. |
Your published apps keep running. The change affects only deploys you start from FlutterFlow, such as Cloud Functions and Firebase rules. Enterprise deployments aren't affected.
Reconnect your Firebase project
Go to Settings & Integrations > Project Setup > Firebase.
In the Reconnect Firebase Project banner, select Reconnect Firebase Project.
Sign in with Google and grant the requested access.
Reconnecting gives FlutterFlow a dedicated service account in your Firebase project, so deploys no longer depend on firebase@flutterflow.io. See the FlutterFlow documentation for the full walkthrough.
After the reconnect succeeds, you can remove the firebase@flutterflow.io principal from every role it holds under IAM in the Google Cloud console. Leave your Firestore rules and Authentication users alone, since the Content Manager signs in with the same address.
Deploy dialog
When you deploy to a Firebase environment that still uses legacy access, FlutterFlow shows a dialog asking you to reconnect. Before October 28, 2026, the dialog offers "Reconnect with Google" and "Deploy anyway." After October 28, 2026, the dialog blocks the deploy until you reconnect.
Emergency access
If you can't reconnect before October 28, 2026, contact support@flutterflow.io to request emergency access for the project. Emergency access lets an existing legacy connection keep deploying until November 30, 2026, but doesn't allow new legacy connections. While emergency access is active, the Reconnect Firebase Project banner shows the end date.
If you see a "Legacy Firebase Access" warning, do not grant new Cloud IAM permissions to firebase@flutterflow.io or remove/recreate the Firebase connection. Instead, go to Settings & Integrations > Project Setup > Firebase and select Reconnect Firebase Project to migrate to a dedicated service account.