Crashlytics
Overview
Crash and error reporting: single/batch report ingest, issue summary, triage (patch), and report detail queries.
API
{pe} = /projects/{projectId}/environments/{environmentId}.
| Method | Path | Notes |
|---|---|---|
| GET | /crashlytics/health | Health |
| POST | /crashlytics{pe}/reports | API key ingest (crashlytics:ingest) |
| POST | /crashlytics{pe}/reports:batch | API key ingest |
| GET | /crashlytics{pe}/summary | JWT |
| GET | /crashlytics{pe}/issues | JWT |
| GET/PATCH | /crashlytics{pe}/issues/{issueId} | JWT |
| GET | /crashlytics{pe}/issues/{issueId}/reports | JWT |
| GET | /crashlytics{pe}/reports/{reportId} | JWT |
Clients
| Package | Runtime |
|---|---|
@vijihub/crashlytics | browser (scoped ingest) |
VijiHub.Crashlytics | .NET |
Implementation
- Enable Crashlytics on the environment.
- Ship a scoped
crashlytics:ingestkey with the client SDK. - Triage issues in Console or via JWT query/patch APIs.
- Prefer batch ingest on mobile burst failures.
Constraints
- Ingest uses scoped keys only in clients.
- Issue management requires JWT.
- Avoid attaching secrets or PII in crash payloads beyond what you intend to store.