Kotlin Android SDK for DebugBundle.

The Android package family provides native Android capture, durable offline delivery, lifecycle breadcrumbs, crash replay, request correlation, and optional UI/network/logging adapters while keeping the host app fail-open.

Android is a mobile client SDK, not a browser relay host. It sends mobile events to the configured ingestion endpoint and uses explicit first-party network instrumentation for trace correlation; browser relay settings such as transportMode, allowedOrigins, and CORS preflight handling belong to the Browser SDK plus a backend/server SDK relay.

Use the BOM so all Android artifacts stay aligned:

dependencies {
    implementation(platform("com.debugbundle:debugbundle-android-bom:1.1.0"))
    implementation("com.debugbundle:debugbundle-android")
    implementation("com.debugbundle:debugbundle-android-okhttp")
}

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

        DebugBundle.init(
            application = this,
            config = DebugBundleConfig(
                projectToken = BuildConfig.DEBUGBUNDLE_TOKEN,
                service = "checkout-android",
                environment = BuildConfig.BUILD_TYPE,
                releaseChannel = BuildConfig.FLAVOR.ifBlank { "production" }
            )
        )
    }
}

Optional OkHttp instrumentation:

val httpClient = OkHttpClient.Builder()
    .addInterceptor(
        DebugBundleOkHttpInterceptor(
            tracePropagationTargets = listOf(DebugBundleTracePropagationTarget.host("api.example.com"))
        )
    )
    .build()

First-event verification:

DebugBundle.captureException(IllegalStateException("android smoke"))
DebugBundle.flush()

Local commands default to a Docker-backed Gradle runner. GitHub Actions uses the Gradle wrapper directly.

make verify
make smoke
make build

Published-artifact smoke:

make smoke-published VERSION=1.1.0

Release publish:

make publish-central VERSION=1.1.0

• Universal Kotlin facade and instance client
• No-throw capture APIs
• Canonical event envelope builder
• Sensitive-field redaction before buffering or transport
• Batching and bounded retry/backoff state
• Duplicate suppression and error_suppressed aggregate emission
• Session sampling and max-events-per-session enforcement
• File-backed offline queue store with TTL and size bounds
• Breadcrumb ring buffer attached to exceptions by default
• Device-context provider abstraction with JVM-safe default snapshot
• Lifecycle-facing recording APIs for screens, app state, and coarse actions
• Configurable log-level filtering and structured log payload metadata
• Coroutine exception handler helper with coroutine-name capture when available
• Chained uncaught-exception capture with bounded next-launch crash replay
• Allowlisted request/response header capture with bodies still off by default
• One-shot /v1/sdk/config fetch with ETag support and explicit refresh hook
• Server-owned capture-policy enforcement for logs, request-event promotion, and standalone breadcrumbs
• Shared propagation-target matcher for native HTTP integrations
• Android runtime bootstrap delegated from the core facade when Android classes are present
• Android-specific config defaults for queue/crash storage and app version metadata
• Android device-context snapshot provider
• Application.ActivityLifecycleCallbacks screen capture
• Process foreground/background breadcrumbs with immediate background flush scheduling
• WorkManager-backed deferred flush worker and scheduler
• Next-launch ANR/process-exit capture from ApplicationExitInfo
• Published BOM for aligned Android SDK dependency versions
• Optional Ktor client plugin with explicit propagation-target matching
• Optional Navigation listener with previous-screen tracking
• Optional Compose screen recorder helpers
• Optional OkHttp interceptor with explicit propagation-target matching
• Optional Timber tree for structured logging capture
• Automatic network breadcrumb capture for instrumented requests
• Policy-driven request-event promotion with preserved trace IDs
• Always-on probe ring buffers with contract-shaped payload.probe_data = { version, items }
• Remote probe directives from GET /v1/sdk/config
• Piggybacked probe_directives parsing from successful ingestion responses
• Standalone probe_event emission for active matching directives
• Heavy-probe dormancy until a matching remote directive or trigger token is active
• HMAC-validated dbundle_probe_... trigger tokens through public helper and OkHttp/Ktor header extraction
• Fake transport test utilities

• Maven Central publishing uses the same Central Portal credentials and in-memory GPG signing secrets already used by the other JVM SDKs.
• CI validates unit and contract coverage, stages artifacts into a temporary Maven repository, and runs a Robolectric consumer smoke install from published coordinates.
• The release workflow verifies full-family published state, publishes the aligned package family, then retries a clean-install smoke against Maven Central until the artifacts propagate.