acra/acra

Application Crash Reports for Android

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 10th, 2026
Created on September 20th, 2012
Open Issues & Pull Requests: 6 (+0)
GitHub issues: Enabled
Number of forks: 1,128
Total Stargazers: 6,503 (+0)
Total Subscribers: 274 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.0 hours
Mean response time: 39.6 hours
90th percentile: 3.7 days
Tracked items: 13

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 14% of issues opened in the past year have been closed. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 561 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (5)
  • documentation (2)
  • enhancement (2)
  • unconfirmed (1)

Most active issues this week

Detailed Description

ACRA is a crash reporting library for Android applications that captures and transmits detailed diagnostic information when apps encounter errors or exceptions.

ACRA solves the problem of limited visibility into application failures by providing developers with comprehensive crash data beyond what the native Android framework offers. When an application crashes, ACRA intercepts the exception, collects detailed information about the device state and error context, and transmits this data to a backend service. The library supports multiple notification modes—silent reports, toast notifications, status bar notifications, or dialogs—allowing developers to control how users are informed of crashes. It can also capture custom variables, debug traces, and breadcrumbs, and send reports for caught exceptions or unexpected application states without requiring an actual crash. Reports are queued locally if network connectivity is unavailable and transmitted when the app restarts.

Developers should adopt this tool if they need crash visibility across Android applications distributed outside the Google Play Store, including beta releases and enterprise private apps, or if they require more granular control over crash reporting behavior and data collection than the native Android framework provides. The library works with all Android versions supported by the official support libraries and integrates with self-hosted backend receivers, giving teams full control over where crash data is stored. It is particularly valuable for applications deployed in regions where Google Play is unavailable or for developers who want to avoid duplicate notifications by suppressing the native Android crash dialog.

The project maintains active test coverage with continuous integration workflows. The library is published to Maven Central, making it readily available for integration into Android projects. Development activity shows ongoing maintenance of compatibility with current Android versions and support library standards.