Version: 1.0.2

Appxiom Issue Callback Listener - Code level Error Detection Notification

The Appxiom SDK provides a powerful callback listener system that enables real-time monitoring of all issues detected in your Android application. Use the Ax.listenForIssue() API to implement custom error handling, logging, or user notification systems.

Step 1: Register the Global Listener

Add the issue listener in your Application class onCreate() method. Register only a single global listener to receive callbacks for all issues detected by the SDK.

Application Class Implementation:

Java
Kotlin

public class MyApplication extends Application {
    @Override
    public void onCreate() {
        super.onCreate();

        // Initialize Appxiom SDK
        Ax.init(this, appKey, platformKey);

        // Register global issue listener
        Ax.listenForIssue(new IssueFoundListener() {
            @Override
            public void issueFoundInBackgroundThread(IssueView issue) {
                // Handle issue detection
                handleIssueDetected(issue);
            }
        });
    }

    private void handleIssueDetected(IssueView issue) {
        // Custom issue handling logic
        Log.d("AppxiomIssue", "Issue detected: " + issue.getDetailedDescription());

        // Switch to UI thread for UI operations
        new Handler(Looper.getMainLooper()).post(() -> {
            // Update UI or show notifications
            showIssueNotification(issue);
        });
    }
}

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()

        // Initialize Appxiom SDK
        Ax.init(this, appKey, platformKey)

        // Register global issue listener
        Ax.listenForIssue { issueView ->
            // Handle issue detection
            handleIssueDetected(issueView)
        }
    }

    private fun handleIssueDetected(issue: IssueView?) {
        issue?.let {
            // Custom issue handling logic
            Log.d("AppxiomIssue", "Issue detected: ${it.detailedDescription}")

            // Switch to UI thread for UI operations
            Handler(Looper.getMainLooper()).post {
                // Update UI or show notifications
                showIssueNotification(it)
            }
        }
    }
}

Step 2: Implement Custom Issue Handling

The callback provides an IssueView object containing issue properties that are synchronized to the server, ensuring complete transparency in the monitoring process.

Important Threading Considerations:

The callback executes in a background thread
Use UI thread (Handler/runOnUiThread) for UI-related operations, if needed.
The callback triggers immediately after issue occurrence

Comprehensive IssueView Field Reference

type

Data Type: byte | Availability: Mandatory for all issues

Identifies the specific type of issue detected. Each issue type has a unique code for easy categorization and handling.

Complete Issue Type Reference:

Type	Category	Description	Documentation
1	Custom	Report Custom Issues	View Details
2	Function	Function returns Null	View Details
3	Function	Function returns value outside range	View Details
4	Function	Function returns unexpected boolean value	View Details
5	Performance	Delayed function execution	View Details
6	Performance	Screen loading delays	View Details
7	Feature	Track feature failures	View Details
8	—	Not Applicable for Android	—
9	Memory	Low memory warning	View Details
10	—	Not Applicable for Android	—
11	Crash	Crash Reporting	View Details
12	Exception	Report Exceptions	View Details
13	Network	Error in Status Code	View Details
14	Network	Exception during network call	View Details
15	Network	Delayed network call	View Details
16	—	Not Applicable for Android	—
17	Memory	Abnormal Memory Usage	View Details
18	Network	Duplicate network call	View Details
19	—	Not Applicable for Android	—
20	Memory	Spike in Memory Usage	View Details
21	Memory	Memory leaks	View Details
22	—	Not Applicable for Android	—
23	Performance	Frozen frames	View Details
24	Performance	Slow frames	View Details
25	ANR	ANR issues	View Details
26	—	Not Applicable for Android	—
27	ANR	Force close due to ANR	View Details
28	—	Not Applicable for Android	—
29	Startup	Cold App Startup delays	View Details
30	Startup	Warm App Startup delays	View Details
31	Startup	Hot App Startup delays	View Details

severity

Data Type: byte | Availability: Mandatory

Indicates the severity level of the detected issue. Available severity levels:

MINOR: Low impact issues
MAJOR: Significant issues affecting functionality
FATAL: Critical issues requiring immediate attention

detailedDescription

Data Type: String | Availability: Mandatory

Descriptive information about the specific event that triggered the issue.

occurrenceTime

Data Type: Long (UNIX Epoch) | Availability: Mandatory

Timestamp indicating when the issue occurred, expressed in milliseconds since the Unix epoch.

location

Data Type: String | Availability: Optional

Geographic or logical location where the issue occurred, useful for distributed applications or location-based debugging.

deviceState

Data Type: JSONObject | Availability: Mandatory

Comprehensive device state information including:

Battery level
Last reboot time
Timezone offset
Available memory
Network connectivity status

customIdentifier

Data Type: String | Availability: Optional

Custom identifier set by the developer using the setCustomId API. Useful for user identification or session tracking. Learn more about custom identifiers.

activityTrail

Data Type: JSONArray | Availability: Optional

Chronologically ordered list of lifecycle events and custom markers, providing context for issue occurrence. Learn more about activity trail.