Firebase
Paste a service-account key once; the assistant reads the config, publishes tested security rules and registers Android fingerprints for Google sign-in.
Updated Oct 16, 2026
Steps
- No Firebase project yet? In the Firebase console, click Create a project (or Add project), name it after the app and wait until it is ready. Google Analytics is optional.
- In the project, create the database once: Build › Firestore Database › Create database, in the location nearest your users. If people sign in, turn the method on under Build › Authentication.
- Open Project settings › Service accounts, click Generate new private key and confirm. A JSON file downloads once.
- In FluxNative, click Server › Backend › Firebase.
- Paste the whole file, starting with
{, and save. Not the Web API key or an OAuth client file.
What the assistant does
- Writes the real app config into the project.
- Tests Firestore and Storage rules before publishing them; rules that fail to compile are refused.
- Registers the Android SHA fingerprint Google sign-in needs, shown in the Build panel under Signing key.
- Stores named secrets in Secret Manager for Cloud Functions.
Good to know
- Android push always goes through Firebase Cloud Messaging, even when the data lives elsewhere. For push alone, Connect Firebase on Push notifications asks only for this key.
- Firestore, sign-in and Cloud Messaging are free on Spark. Storage, Cloud Functions and Secret Manager need the Blaze plan, with a card on file.
- The test says the key works but lacks permission? A project owner presses Open IAM in Google Cloud under the connection, then Grant access, pastes the account (the file's
client_email), picks Firebase Admin and saves. Test again a few minutes later. - Generate new private key says key creation is disabled? The Google Cloud organization blocks keys, the default for organizations made since May 2024: an organization admin allows them for this project.
Related
Did this page help?