Firebase during publishing
When you publish your app and the Firebase module is active, the wizard shows a Firebase step. Here you provide the service account of your Firebase project — this lets BLOCQ set up all Firebase services automatically during publishing.
What happens in the publish step
Section titled “What happens in the publish step”| Step | Description | Effort |
|---|---|---|
| Set up service account | Create a Google Cloud service account with the required roles | ~10 min |
| Upload service account JSON | Upload the JSON file; the app validates the connection | ~2 min |
The flow
Section titled “The flow”The Firebase step shows a service account card with a status (configured / not configured yet). Tap it to open the guided service account assistant.
-
Create the service account
Tap the service account card. The guided assistant opens the Google Cloud Console right inside the app and walks you through creating a service account with the required roles.
Detailed guide: Set up a service account
-
Upload the service account JSON
Upload the service account’s JSON file. The app validates the connection automatically. Once it’s valid, the card turns green and you can continue.
What does this replace?
Section titled “What does this replace?”Previously you had to set up Firebase before activating a module:
| Before | Now |
|---|---|
| Create the Firebase project before the first module | Create the Firebase project during publishing |
| Copy Firestore rules manually | Rules are deployed automatically |
| Copy storage rules manually | Rules are deployed automatically |
| Create indexes manually | Indexes are created automatically |
| Manual or automatic setup per module | Everything at once, fully automatic |
After the Firebase setup
Section titled “After the Firebase setup”Once the Firebase setup is complete, the Auto-Setup Runner starts automatically. It configures all active modules:
- Firestore security rules for all active modules
- Storage security rules
- Firestore indexes
- Auth methods
- Admin account
- Data migration
You don’t need to do anything else — the runner handles everything automatically.
Troubleshooting
Section titled “Troubleshooting””Invalid config file”
Section titled “”Invalid config file””Problem: The uploaded plist or json file is not accepted.
Solutions:
- Make sure you selected the correct file
- Check that the file belongs to the correct Firebase project
- Download the file again from the Firebase Console
”Service account connection failed”
Section titled “”Service account connection failed””Problem: The connection to the service account cannot be established.
Solutions:
- Check that all 7 roles were assigned correctly
- Make sure the JSON file was downloaded completely
- Wait a few minutes — new permissions sometimes take time to take effect