Appxiom Integration Troubleshooting - Fix SDK Issues

Quick Resolution: Follow these systematic steps to resolve common Appxiom SDK integration issues.

If test issues created using the integration code below are not appearing in your Appxiom dashboard, follow these troubleshooting steps to identify and resolve the problem.

Need help? Raise a ticket at: support.appxiom.com

Java

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

        Ax.log();
        Ax.init(this, appKey, platformKey);

        Ax.test();
    }
}

Kotlin

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

        Ax.log()
        Ax.init(this, appKey, platformKey)

        Ax.test()
    }
}

Systematic Troubleshooting Steps

Step 1: Verify Basic SDK Configuration

Check SDK Version and Setup:

• Ensure you are using the latest Appxiom SDK version
• Verify that Ax.log() is called before Ax.init()
• Ensure your Application class (e.g., BlogApp) is registered in your AndroidManifest.xml

Application Manifest Registration:

<application
    android:name=".BlogApp"
    android:label="@string/app_name"
    android:theme="@style/AppTheme">
    <!-- Your activities and other components -->
</application>

Step 2: Perform Clean Installation

Remove Previous Installations:

1. Completely uninstall any existing app instance from your emulator or device
2. Clear app data if the uninstall doesn't remove all traces
3. Run a fresh installation of your application
4. Launch the app and check for test issues in the dashboard

Why This Helps: Previous installations may have cached invalid configurations or registration states that prevent proper SDK initialization.

Step 3: Verify SDK Activation

Check for Registration Log: Look for this log message in your Logcat:

About to make register device request

If Missing Registration Log:

• Verify that Ax.init() is actually called in your Application class onCreate() method
• Confirm your Application class is properly registered in AndroidManifest.xml
• Check that your Application class constructor and onCreate() method is not throwing exceptions

Debug Application Class:

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

Step 4: Analyze Error Logs

Common Registration Errors:

Status Code 401 - Authentication Failed:

• Cause: Package name mismatch between your app and Appxiom dashboard configuration
• Solution: Ensure the package name in your build.gradle (applicationId) exactly matches the app configuration in Appxiom dashboard
• Verification: Check build.gradle (Module: app) for the correct applicationId

android {
    defaultConfig {
        applicationId "com.yourcompany.yourapp"  // Must match value added in Appxiom dashboard
        // other configuration
    }
}

Other Status Codes:

• Status Code 403: App not properly configured in dashboard
• Status Code 500: Server-side issues (contact support)

Step 5: Network and Connectivity Verification

Network Troubleshooting:

1. Check Internet Connection: Ensure your device has active internet connectivity
2. WiFi Restrictions: If using WiFi, verify there are no corporate or public network restrictions
3. Firewall Issues: Some workplace or public WiFi networks block SDK communication
4. Alternative Connection: Switch to mobile data (3G/4G/5G) for testing

Network Testing Steps:

1. Switch to mobile data connection
2. Uninstall the existing app completely
3. Reinstall and launch the application
4. Check if test issues now appear in the Appxiom dashboard

Need help? Raise a ticket at: support.appxiom.com