Skip to main content

Troubleshooting

Common issues and solutions for the Pulse Android SDK.

SDK Not Initialized​

Symptoms​

If you see warnings about the SDK not being initialized:

  • No telemetry being sent
  • Logcat warnings about SDK not initialized

Solution​

  1. Ensure PulseSDK.INSTANCE.initialize() is called in your Application.onCreate()
  2. Check that the initialization happens before any other SDK calls
class MainApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        // Initialize early
        PulseSDK.INSTANCE.initialize(
            application = this,
            projectId = "your-project-id"
        )
    }
}

No Telemetry Being Sent​

Possible Causes​

  • Network connectivity issues
  • Disk buffering disabled when offline

Solution​

  1. Check network connectivity
  2. Check Android logcat for error messages
  3. Ensure disk buffering is enabled if you're testing offline scenarios:
PulseSDK.INSTANCE.initialize(
    application = this,
    projectId = "your-project-id",
    diskBuffering = {
        enabled(true)
    }
)

Performance Impact​

The SDK is designed for minimal overhead, but you can optimize:

Solutions​

  • Disable unused instrumentations
  • Adjust sampling rates if needed
  • Monitor SDK performance metrics
PulseSDK.INSTANCE.initialize(
    application = this,
    projectId = "your-project-id",
) {
    // Disable instrumentations you don't need
    fragment { enabled(false) }
}

Still Having Issues?​

If you're still experiencing issues:

  1. Check the API Reference for correct usage
  2. Review the instrumentation guides for recommended patterns
  3. Contact Pulse support at support@pulse-ux.com

Next Steps​

  • Review the instrumentation guides for recommended patterns
  • Check the API Reference for detailed method documentation