ElmonyDocs

Integrations

Firebase

The Firebase panel guides an app through Google authorization, project selection, Auth, Firestore, Storage, security rules, and native mobile configuration.

Setup

Open the project in Builder and select Firebase. Complete the checklist in order; later steps depend on the account and project saved in the earlier steps.

  1. Connect the Google account Elmony should use for Firebase API access.
  2. Choose an existing Firebase project or create a new one, then save its Web app configuration.
  3. Enable the Firebase Management API and the sign-in providers the app uses.
  4. Enable Firestore and the Firebase Rules API, create or verify the database, and publish reviewed rules.
  5. If the app stores files, configure the bucket, enable Storage, and publish reviewed Storage rules.
  6. For mobile production builds, confirm the package name and bundle identifier and sync native Firebase config files.

Project scope

A project can use Firebase configuration isolated to that app or reuse the shared Firebase configuration. Use an app-specific project for production isolation. Before switching a shared account or project, check every app that depends on it.

Authentication

Enable only the providers the app needs. Google sign-in requires the Web client ID; a mobile Android release also needs the signing certificate SHA-1 registered in Firebase.

Firestore and Storage

Elmony can enable services and deploy rules, but you remain responsible for reviewing access control. Test owner-only assumptions, anonymous access, and administrative paths.

Mobile production configuration

Load or review the Expo production identifiers, add Android SHA-1 fingerprints when needed, and use the native sync action to write the Android and iOS Firebase configuration used by EAS production builds. Repeat native sync after changing identifiers or Firebase apps.

Troubleshooting

  • If automatic setup reports an API error, open the provided Google Cloud link, enable the named service for the selected project, wait for propagation, and retry.
  • If project creation is rate-limited, wait for the cooldown shown in the panel or choose an existing Firebase project.
  • If Google login works in preview but fails in Android release, verify the package name, production keystore SHA-1, OAuth client, and synced native configuration.
  • If reads or uploads fail, inspect Firestore or Storage rules before loosening them. Avoid using broad public rules as a permanent fix.