Skip to main content
Version: 1.0.0

Appxiom SDK Logging - Enable and Manage Appxiom Logs for Debugging

Appxiom SDK provides a simple way to activate internal logging for enhanced debugging and monitoring during development. Enabling Appxiom logs allows you to view all SDK-related logs, including errors and warnings, directly in Logcat.

Activate internal SDK logging with a single API call for better visibility into Appxiom operations.

How to Enable Appxiom SDK Logging

Call the Ax.log() API in your Application class to enable SDK logging. This will print all internal Appxiom logs to Logcat, helping you diagnose integration issues and monitor SDK behavior.

Example: Application Class Integration

public class BlogApp extends Application {
@Override
public void onCreate() {
super.onCreate();
Ax.log();
Ax.init(this, appKey, platformKey);
}
}

Important: Remove the Ax.log() API call before releasing your app to production to avoid exposing internal logs.

Best Practices for SDK Logging

  • Enable logging only in development and testing builds.
  • Remove or disable logging in production releases to prevent exposure of internal SDK operations and sensitive information.

Frequently Asked Questions (FAQ)

Q: What does Ax.log() do?
A: It enables internal SDK logging, printing all Appxiom logs, errors, and warnings to Logcat for easier debugging and monitoring.

Q: Where should I call Ax.log()?
A: Call it in the onCreate() method of your Application class before initializing the SDK.

Q: Should I keep Ax.log() in production builds?
A: No, always remove or disable the log API before releasing your app to production to prevent internal logs from being exposed.

Q: Will enabling Appxiom logs affect app performance?
A: Logging is lightweight and intended for development and debugging. It should be disabled in production for optimal performance and security.