Overview
A saved Firebase record is not automatically proof that Firebase accepts it.
PulseGrid uses clear states:
- Saved / not verified: configuration exists but verification has not succeeded yet.
- Verified: Google accepted the saved service-account credential.
- Needs attention: verification failed and the credential/project must be checked.
The Firebase project ID in the service-account JSON should match the Firebase project used by the receiving application.
Setup
1. Open Firebase Console and select the application's Firebase project.
2. Open Project settings -> Service accounts.
3. Generate a new private key when needed.
4. Keep the downloaded JSON private.
5. In PulseGrid, open Push and select the matching PulseGrid project.
6. Open Manage Firebase.
7. Paste the complete service-account JSON.
8. Save and verify.
9. Confirm the UI says Firebase verified.
10. If an older imported connection exists, verify it once and replace it if it belongs to the wrong Firebase project.
Code example
A service-account file has fields similar to:
{
"type": "service_account",
"project_id": "your-firebase-project-id",
"private_key_id": "...",
"private_key": "-----BEGIN PRIVATE KEY-----...",
"client_email": "firebase-adminsdk-...@your-project.iam.gserviceaccount.com"
}
Use the real downloaded JSON. Do not copy this example.Notes
Verification proves server authentication to Firebase. It does not prove a particular phone/browser will display a notification. The client still needs permission, a valid token and correct foreground/background handling.