ACRA/acra
Acra
Acra is an Android crash reporting framework and diagnostic data collector designed to detect failures and capture device diagnostics, system logs, and application state. It serves as an embeddable library for capturing and processing crash reports, providing a pipeline to send this data to custom backends or via email.
The project features a plugin-based sender architecture that allows reports to be routed through HTTP endpoints, email clients, or proprietary backend implementations. It includes a user-controlled reporting system with preference toggles and interactive dialogs to manage user consent and report frequency.
The framework covers a broad range of diagnostic capabilities, including the collection of system logcat output, device identifiers, and application preferences. It manages the report lifecycle through file-based persistence and synchronized queuing to ensure delivery after application restarts. The system also includes security primitives for report encryption and traffic management to limit the frequency of reports sent from a single device.
Features
- Crash Reporting - Provides a comprehensive framework for collecting and managing crash reports from Android applications.
- Delivery Senders - Provides a pluggable architecture for routing crash reports through HTTP, email, or custom backends.
- Crash Diagnostics - Collects application logs, system events, and device metadata to provide deep context for debugging failures.
- Consent Management - Provides preference toggles for users to manage consent for reporting and data collection.
- Metadata Attachments - Adds key-value traces and breadcrumbs to reports to track events leading to failure.
- Reporting Plugins - Defines a pluggable sender interface allowing custom implementations for HTTP, email, or proprietary backends.
- Local Report Persistence - Persists crash reports as files on disk before transmission to enable recovery after application restarts.
- Report Delivery Routing - Routes crash data through HTTP endpoints, email clients, or custom backends with support for offline queuing.
- Crash Reporters - Collects detailed device and error data during an application failure and transmits it to a backend.
- Telemetry and Log Collectors - Extracts system logcat output, device identifiers, and application preferences without relying on reflection.
- Application Logging - Appends the latest lines from custom application log files to generated crash reports.
- Android System Log Captures - Extracts and filters system logcat output from Android devices to provide diagnostic context for crashes.
- Scheduled Report Deliveries - Schedules report transmission based on network availability and ensures delivery after application restarts.
- System - Collects persisted system-tagged events from the Android DropBoxManager for deep failure diagnostics.
- Application Preferences - Collects application preference files for inclusion in crash reports with privacy filtering.
- User Preference Configurations - Uses SharedPreferences to store user consent and data exclusion rules for runtime control.
- Android Configuration Management - Stores report toggles and sensitive key exclusions within Android SharedPreferences.
- User-Facing Consent Dialogs - Shows a customizable dialog requesting user consent and optional comments before sending reports.
- Device Identification Utilities - Adds unique hardware identifiers to reports for device-level tracking.
- Interactive Report Notifications - Triggers a system notification that allows users to send or discard a report with optional comments.
- Sensitive Data Protection - Implements privacy protection by removing sensitive preference keys matching regular expressions from crash reports.
- UI Lifecycle Integration - Triggers crash dialogs only when the application is in the foreground to avoid memory leaks.
- Synchronized Queues - Uses a thread-safe queue to manage the flow of reports during concurrent background transmission.
- File-Based Persistence - Persists captured crash data to local disk to ensure delivery after application restarts.
- Crash Submission Interfaces - Displays a dialog after a failure that allows users to add comments to the report.
- Customizable Report Schemas - Allows developers to define which specific data fields and system information are collected.
- Pluggable Report Senders - Implements a plugin-based architecture for routing crash data via HTTP, email, or proprietary backends.
- Error Reporting - Allows manual reporting of exceptions caught in try-catch blocks or other unexpected application states.
- Report Rate Limiting - Restricts the number of reports sent from a single device to prevent backend flooding.
- Arbitrary File Attachments - Includes specific device files via URIs or content providers as report attachments.
- User-Controlled Reporting Interfaces - Provides preference toggles and interactive dialogs for managing user consent and crash report frequency.
- Mobile Email Routing - Delivers crash reports via the device email client to avoid requiring internet permissions.
- ProGuard Configurations - Provides crash reporting configuration rules.
- Testing and Debugging Tools - Library for automated crash reporting and diagnostics.
- Mobile UI & Components - Application Crash Reports for Android
