Overview
xcrashlytics brings production crash context into the terminal so developers and coding agents can investigate failures alongside the relevant source code. It works with Firebase Crashlytics applications across iOS, Android, macOS, and other supported platforms, and can also read iOS reports already downloaded by Xcode Organizer.
The tool focuses on retrieving and organizing crash evidence rather than diagnosing defects or changing code. This distinction lets an agent inspect concrete data while leaving technical conclusions and repairs to the surrounding development workflow.
Key Features
- Searches crash issues by feature, error, or application version.
- Displays crash messages, stack traces, and application frames.
- Breaks down exact event and user counts by version.
- Exposes structured JSON for use by coding agents.
- Exports investigation findings as Markdown reports for team sharing.
- Checks warnings and follows an investigation contract intended for agent workflows.
Investigation Workflow
A typical investigation starts by locating an issue related to a feature or release, then following its stack to the relevant application frames. Impact data can be grouped by version to show how widespread the issue is and help identify the release in which it appeared.
Once the evidence is available, a developer or coding agent can compare it with the repository's code and prepare a report. xcrashlytics supplies the crash context but does not claim to identify or implement the fix automatically.
Installation Context
xcrashlytics is distributed for macOS and can be installed through its installer, Homebrew, a direct release download, or from source. The installer places the executable in the user's local binary directory, verifies its checksum, and does not require elevated privileges. Firebase CLI is also required for Firebase-backed crash access.