Oynix
Crashlytics

Connectors / Firebase Crashlytics

Crashes, with the frames that point to your code.

Read your Crashlytics crash groups from their BigQuery export and link each one to the code frames behind it. Read-only, and your data stays in your boundary (BYODB).

A token you paste

Before you start

Install Oynix and open the connectors page. You do this once. Everything below then happens right in the page, with no commands to run.

Install OynixOpen the connectors page

Log in

This source connects one way.

A token you paste

Paste a credential.

  1. 1Create the credential: in the Firebase console make the service-account JSON, then Project Settings → Integrations → BigQuery → Link and tick Crashlytics to export, and grant that account BigQuery Data Viewer and Job User in Cloud IAM.
  2. 2Open Firebase Crashlytics in the connectors page and choose the token path.
  3. 3Enter the service-account JSON, the GCP project id, and the dataset if it is not the default, then click Connect. Oynix checks it right then and saves nothing if it fails.

After login

Once connected, this all happens in the page. No commands.

  1. 1The picker opens. Choose which apps to sync (each app exports its own crash tables) to sync.
  2. 2Hit Sync to pull just those into the graph and link them to your code.
  3. 3Deselect one later and Oynix purges only that instance's data.

The service account needs BigQuery Data Viewer and Job User. The export must be enabled, and the first daily batch can take up to ~24h to land. Until it does, the connector reads as pending, not a false green.

What it syncs

Crash issues

One document per grouped crash: exception, full stack frames and a per-version breakdown.

Code frames

The stack frames that link each crash back to your code.

Signals

First-seen, distinct devices and a banded count.

This is the one connector that can sit connected but not syncable yet while the export lands, so the page lets you re-check it.