Android Crash Reporting - Automatic Exception Tracking

Automatic Detection: Crash reporting is enabled by default and works in both debug and release builds.

Issue Classification: Type: 11 | Severity: FATAL

The Appxiom SDK provides comprehensive crash reporting capabilities that automatically detect and report uncaught exceptions in your Android application. This essential monitoring feature helps you identify stability issues and improve your app's reliability.

Crash Data Collected:

• Complete stack trace with line numbers (if available)
• Exception type and error message
• Device state at time of crash
• User activity trail leading to crash
• Memory usage and system information

When a crash occurs, the SDK immediately:

1. Captures Exception Details: Full stack trace and error context
2. Records Device State: Memory, battery, network status
3. Saves Activity Trail: User actions leading to the crash
4. Queues for Transmission: Crash data sent on next app launch

Basic Setup

Crash reporting is automatically enabled when you initialize the Appxiom SDK:

Java

public class MyApplication extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        
        // Crash reporting automatically enabled
        Ax.init(this, appKey, platformKey);
    }
}

Kotlin

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        
        // Crash reporting automatically enabled
        Ax.init(this, appKey, platformKey)
    }
}

Disabling Crash Reporting

If you need to disable crash reporting, use the disableCrashReporting parameter in the @AX annotation:

Java

@AX(disableCrashReporting = true)
public class MyApplication extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        Ax.init(this, appKey, platformKey);
    }
}

Kotlin

@AX(disableCrashReporting = true)
class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        Ax.init(this, appKey, platformKey)
    }
}

---

Frequently Asked Questions (FAQ)

Q: Is crash reporting automatically enabled in the Appxiom SDK?

A: Yes, crash reporting is automatically enabled when you initialize the Appxiom SDK. No additional configuration is required for crash detection.

Q: Does crash reporting work in debug builds?

A: Yes, crash reporting works in both debug and release builds, allowing you to catch crashes during development and in production.

Q: Can I enable crash reporting for specific parts of my app only?

A: No, crash reporting is a global feature. It's either enabled or disabled for the entire application. Use the callback system to filter crash handling if needed.

Q: What information is captured when a crash occurs?

A: The SDK captures complete stack traces, exception details, device state, memory usage, battery level, network status, and user activity trail leading to the crash.

Q: How quickly are crashes reported to the dashboard?

A: Crashes are queued immediately when they occur and transmitted to the dashboard on the next app launch.

Q: Are stack traces obfuscated in release builds?

A: Stack traces reflect your build configuration. If you use ProGuard or R8 obfuscation, stack traces will be obfuscated View Details.

Q: Can I use Appxiom crash reporting alongside Firebase Crashlytics?

A: Yes, you can use both services simultaneously.

Q: How do I handle crashes that occur during app initialization?

A: Ensure Ax.init() is called as early as possible in your Application.onCreate() method to capture initialization crashes.

Q: What personally identifiable information is included in crash reports?

A: By default, no PII is collected. Only technical crash data, device state, and activity trails are captured. Avoid including sensitive data in custom identifiers.

Q: How is crash data transmitted and stored?

A: Crash data is encrypted during transmission and securely stored. The SDK follows security best practices for sensitive crash information.

---