Firebase Crashlytics Integration

Overview

The Firebase Crashlytics integration uses a webhook to forward crash alerts from Firebase to ReleaseTag. When a new crash, non-fatal error, ANR, or regression is detected by Crashlytics, the ReleaseTag Firebase extension sends the alert to your project, where it appears in your Diagnostics tab.

What syncs

• New fatal crashes
• New non-fatal errors
• ANR (Application Not Responding) issues
• Regression alerts (previously closed issues resurfacing)

Prerequisites

• A ReleaseTag account with admin or owner access to your project
• A Firebase project with Crashlytics enabled
• Permission to install Firebase extensions

Installation

Step 1: Enable the webhook in ReleaseTag

1. Go to Project Settings → Integrations
2. Find the Firebase Crashlytics section
3. Click Enable Crashlytics Webhook
4. Copy the Webhook URL and Authorization Header Secret that are generated

Step 2: Install the ReleaseTag Crashlytics Extension

1. Open the ReleaseTag extension install page in the Firebase Console
2. Select your Firebase project
3. When prompted, enter the Webhook URL and Webhook Secret you copied from ReleaseTag
4. Select your preferred Cloud Functions location and complete the installation

Viewing Crashlytics data

Crashlytics alerts appear in the Diagnostics tab of your project dashboard. Each entry shows crash details forwarded by the Firebase extension.

Managing the integration

Regenerating the secret

If the webhook secret has been compromised, you can regenerate it:

1. Go to Project Settings → Integrations
2. Find the Firebase Crashlytics section
3. Click Regenerate Secret
4. Update the authorization header in the Firebase extension configuration with the new secret

The old secret will stop working immediately.

Disabling the integration

To stop receiving Crashlytics alerts, either:

• Uninstall the ReleaseTag Crashlytics extension from your Firebase project
• Or reconfigure the extension and clear the webhook URL

Troubleshooting

Alerts not appearing

• Verify the webhook URL and secret are correctly configured in the extension
• Make sure the ReleaseTag Crashlytics extension is installed and running
• Check that Crashlytics is enabled in your Firebase project and is receiving crashes
• The extension only forwards new alerts — historical crashes are not synced

Privacy & Security

• Webhook payloads are authenticated using a Bearer token
• Only crash metadata is received (error type, message, location)
• No user data or device identifiers are stored
• You can revoke access at any time by regenerating the secret or uninstalling the extension

Support

Having trouble? Contact us at support@releasetag.com