Skip to main content

Release notes (7.x Beta)

Beta

Bugsee Android SDK 7.x is currently in beta. APIs, options, and the Gradle plugin contract may still change before the stable release. For production workloads, consider staying on the 6.x line. See the migration guide when planning your upgrade.

7.0.0-beta8​

This release adds an exchange factory for constructing Breadcrumb and NetworkEvent containers without allocating them yourself, makes hang detection thresholds configurable, and reduces GC pressure on the network-event fallback path.

New features

  • Bugsee.getExchangeFactory() — returns a shared BugseeExchangeFactory for constructing the exchange objects you pass to addBreadcrumb and addNetworkEvent. The factory delegates to the SDK's pooled capture-side containers, so you do not allocate per event:
  • createBreadcrumb() / createBreadcrumb(timestamp, category, message, level, type, data) — short and fully-populated overloads for breadcrumbs.
  • createNetworkEvent(timestamp, stage, id, mechanism, httpMethod) plus a fully-populated 16-argument overload covering URL, headers, body, response code, error fields, and timings.

Each create* method may return null when the underlying capture subsystem isn't yet available (for example, before launch) — always null-check. Once populated, hand the returned object to the matching Bugsee.add* method and don't retain it: instances are pooled and the SDK recycles them after submission.

  • Configurable hang detection thresholds. Three new options control the millisecond thresholds that trigger Fair, Medium, and Severe hang reports. Previously these were hardcoded to 3 s, 5 s, and 10 s.
  • Options.DetectAndReportHangFairLevel (default 3000)
  • Options.DetectAndReportHangMediumLevel (default 5000)
  • Options.DetectAndReportHangSevereLevel (default 10000)

Thresholds must be strictly increasing and positive; invalid configurations fall back to the documented defaults. Detection resolution is approximately 1 second — values smaller than that are rounded up by the watchdog tick. See Detection → Hang detection.

Improvements

  • The fallback NetworkEvent allocation path used when no capture-side pool entry is available now reuses instances via an intrusive 15-slot free list. Producers see no API change; the SDK's network coordinator recycles each instance after dispatch, eliminating allocation churn for hub-only consumers (APM, extension listeners) when the network capture provider isn't running.
  • Network event listeners (NetworkEventListener.onNetworkEvent) now have an explicit "do not retain past the callback" clause in the contract — matching the long-standing log-listener convention. The event instance may be pooled and reused for a subsequent network event; copy any values that need to outlive the callback.

Build

  • No Gradle plugin upgrade required — continues to work with 4.0.0-beta4 or newer.

7.0.0-beta7​

This release adds three small public APIs for inspecting blackout state and injecting custom network events and breadcrumbs into the capture pipeline.

New features

  • Bugsee.isBlackout() — returns true while a complete blackout is active (i.e. between startBlackout() and endBlackout()). Reads the same state the existing pair already manages, with no separate cache; safe to call before launch.
  • Bugsee.addNetworkEvent(NetworkEvent, boolean) — record a NetworkEvent produced outside of the SDK's built-in interception (custom HTTP clients, native bridges, hand-built request/response pairs). The event is forwarded to the same capture pipeline that automatically intercepted events go through, so it appears in reports and session recordings alongside them. The requiresFiltering flag controls whether the event is run through the registered setNetworkEventFilter — pass true for raw payloads that may need redaction, false when the caller has already sanitized the event. See Network events.
  • Bugsee.addBreadcrumb(Breadcrumb) — record a Breadcrumb produced outside of the SDK's automatic breadcrumb sources (custom navigation events, business-domain checkpoints, breadcrumbs forwarded from a wrapper SDK). The breadcrumb runs through the registered setBreadcrumbFilter before being recorded. See Privacy → Breadcrumbs.

Improvements

  • The internal network-event delivery path now goes directly to the shared network interception coordinator rather than resolving the consumer through the capture coordinator on every call. No behavior change for SDK users; one fewer hop on the producer hot path.

Build

  • No Gradle plugin upgrade required — continues to work with 4.0.0-beta4 or newer.

7.0.0-beta6​

This release introduces anomaly detection, splits NDK crash reporting into its own optional module, and consolidates how the SDK captures logs, network, input, and WebView events.

Breaking changes

  • Native (NDK) crash detection now ships as a separate bugsee-android-ndk extension. Apps that need native crash capture must add implementation("com.bugsee:bugsee-android-ndk:7.x.x") and switch from Options.DetectAndReportCrashNdk to NdkOptions.DetectAndReport. The underlying option key is unchanged. See the updated Crashes guide.
  • The legacy WebView capture provider has been removed. WebView content now flows through the new unified interception layer, so no action is needed beyond updating to this version.

New features

  • Anomaly detection. A new built-in provider watches APM transactions and surfaces statistical outliers — using exponentially weighted mean/variance baselines maintained per bucket (e.g. HTTP method + host + path template) and a z-score threshold. High-severity outliers are reported as errors; medium-severity ones as breadcrumbs. Off by default — enable with Options.DetectAndReportAnomaly and ensure APM is on. Baselines persist across sessions.
  • Breadcrumb filtering. A new public Bugsee.setBreadcrumbFilter(...) lets you inspect, modify, or drop breadcrumbs before they're recorded — mirroring the existing log and network filters. The previous hardcoded URL sanitization on HTTP breadcrumbs has been removed in favour of this user-controlled filter. See Privacy → Breadcrumbs.
  • Adaptive APM sampling. A new Options.PerformanceAdaptiveSampling option (on by default) lets the SDK automatically tune transaction sampling based on observed traffic.
  • Richer NDK crash reports. Native crashes are now matched against the system's historical exit records, attaching the matching tombstone to the report when one is available.
  • Extension APIs. New public hooks let extension modules listen for completed transactions, log events, and input events, and register custom capture data entries synchronously at startup.
  • Breadcrumbs. HTTP-request breadcrumbs now carry a mechanism field, and producer types have been aligned with the icons shown in the report viewer.
  • New optional :ai base module providing a TfliteModel abstraction. Reserved for a future AI-based anomaly detection extension; the built-in anomaly detector that ships today is purely statistical.

Improvements

  • A new unified interception layer routes logs, network calls, input events, and WebView traffic through shared hubs, so capture and APM no longer duplicate work.
  • Extension content providers initialize in a guaranteed order relative to the core SDK.
  • WebView debugging initialization no longer runs on a background thread.

Fixes

  • Secure views no longer leak a single frame around asynchronous screen captures.
  • The V2 video encoder no longer stalls under load.
  • ANR and NDK trace payloads are smaller and contain less duplicate data.
  • Bluetooth state is now reported as "unknown" on error rather than being dropped.
  • Updated ProGuard rules keep extension-facing APIs intact through R8.
  • Internal option keys on the wire now match the backend's expected format.

Build

  • Requires the Bugsee Android Gradle plugin 4.0.0-beta4 or newer.
  • Adds new :ndk and :ai modules and enables Bugsee's own build size analysis in CI.
  • Expanded test coverage: end-to-end tests for anomaly detection, load tests across all interception paths, and new encoder and leak benchmarks.

7.0.0-beta5​

  • Network monitoring is now driven by a single shared coordinator consumed by both capture and APM, removing duplicated work between the two pipelines.
  • A new capture data entry registry eliminates a class of startup race conditions around provider and exporter discovery.
  • Requires the Bugsee Android Gradle plugin 4.0.0-beta2 or newer.
  • Adds comprehensive instrumentation tests for network interception.

7.0.0-beta4​

This release focuses on startup performance and resource footprint.

  • Capture sources, codec metadata, HTTP connection pools, and internal thread pools all initialize lazily or with leaner defaults, reducing startup overhead and steady-state resource use.
  • The first captured frame is now tied to a launch timestamp recorded earlier in the process, tightening alignment between launch and the first frame.
  • Improves thread safety of listener management in tracker internals.
  • Removes a redundant back-press override in the feedback activity.
  • Adds behavioral tests for the connection and thread pool configurations.

7.0.0-beta3​

  • Cold start is faster — non-critical initialization has been moved off the startup path.
  • The feedback activity now supports Android's predictive back gesture.
  • Fix: Provider discovery in minified builds — runtime annotations used by capture and detection are now preserved through ProGuard/R8.
  • Adds annotation-integrity checks and release-AAR verification to the test suite.

7.0.0-beta2​

  • All SDK modules are now published to Maven Central as bugsee-android-* artifacts (core, feedback, okhttp, ktor-2, ktor-3, cronet, compose), with proper Javadoc and source JARs.
  • All extension modules are now built with R8 minification and self-obfuscation enabled.
  • The public API surface is now validated and tracked using the Kotlin Binary Compatibility Validator; obfuscated classes are filtered out of the surface.
  • Detection contracts have been refined and stabilized for the public API.
  • Fix: ProGuard rules updated to keep capture data classes, exporter constructors, and the LZ4 / XXHash JNI-bound classes from being stripped.
  • Requires the Bugsee Android Gradle plugin 4.0.0-beta1 or newer.
  • Adds fuzz tests for capture data entries, core utilities, native components, and the screen-capture bitmap cache.

7.0.0-beta1​

First public beta of the 7.x line — a ground-up rewrite of every major subsystem.

What's new

  • Multi-display and foldable support. Each display is tracked independently and composited into the report.
  • New screen capture engine. Multiple strategies are selected automatically based on device, Android version, and display, with encoding decoupled from the capture thread.
  • Modular detection. Independent providers for Java/Kotlin crashes, native (NDK) crashes via Breakpad, hangs, abnormal exits (ANR/OOM/user-stop/package-update), and main-thread misuse.
  • Expanded system telemetry. 9 system event types and 23 system trace types covering display state, thermal, connectivity, FPS, memory, power, orientation, UI mode, and more.
  • Breadcrumb capture (beta). Built-in app, UI, network, and system breadcrumb sources, opt-in via CaptureBreadcrumbs.
  • Modular architecture. A core library plus separate extension modules for feedback and HTTP clients (OkHttp, Ktor 2, Ktor 3, Cronet, Jetpack Compose). Extensions auto-register at startup.
  • Automatic initialization. Adding the com.bugsee.app-token manifest entry is enough to launch the SDK; programmatic launch with async completion callbacks is still supported.
  • Application Performance Monitoring. Built-in providers for UI load/display, cold-start, HTTP, database, and file I/O, plus custom Transaction and Span APIs that propagate context across threads.
  • New Gradle plugin (4.0.0-beta1) — required. Provides bytecode instrumentation for logcat, OkHttp, HttpEngine, Compose touch capture, native threads, and APM, plus mapping/NDK-symbol upload and extension auto-install.

Breaking changes

  • LaunchOptions is gone — configure via a Map<String, Serializable> keyed by Options.* constants, or via manifest meta-data.
  • Network-client helpers for OkHttp, Ktor, and Picasso have been replaced by extension modules. OkHttp 2 is no longer supported.
  • Feedback now lives in the bugsee-android-feedback extension; access it via Bugsee.ext(Feedback.class).
  • Option keys have been renamed across detection, capture, reporting UI, and trigger groups. IssueSeverity.Critical has been removed.
  • pause(), resume(), and isResumed() have been replaced by the blackout APIs startBlackout() and endBlackout().
  • getDeviceId(), setEmail(), and getEmail() have been removed. Use setUserIdentifier() / getUserIdentifier() / clearUserIdentifier().
  • The ExtendedReport / ExtendedReportCreatedListener / setReportFieldsFilter / setReportAttachmentsProvider APIs are replaced by the new Report and ReportHandler contracts. createReport(...) is unchanged; a new showReportDialog(...) API has been added for opening the report UI directly.
  • The public-field BugseeAppearance is replaced by the typed Appearance contract with setColor and setString accessors.

See the migration guide for a complete change-by-change walkthrough.