From b28f536d4595472506cb83ca38db9df94914ed0a Mon Sep 17 00:00:00 2001 From: Alexey Karimov Date: Thu, 20 Aug 2026 11:31:09 +0500 Subject: [PATCH 1/2] docs(android): add 7.1.2 release notes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Native crash reporting release: the uncovered window at the start of the first launch after an install or update, crashes that kill the app before it can report, reports assembled before capture was running, and a damaged handler that looked healthy while producing nothing. Also the addSecureView/removeSecureView signature change, with a note that it needs a rebuild rather than an AAR swap — passing a fragment is unchanged otherwise. Leaves out the WebView work in this version: it is inert until the matching JavaScript package ships, so documenting it now would describe behavior nobody can observe yet. Change-Id: I2e27a192a2b1656b87b240fe22fe308f48e36e89 --- docs/sdk/android/release-notes.md | 46 +++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/docs/sdk/android/release-notes.md b/docs/sdk/android/release-notes.md index 30e36a6..b1d06f0 100644 --- a/docs/sdk/android/release-notes.md +++ b/docs/sdk/android/release-notes.md @@ -7,6 +7,52 @@ slug: "/sdk/android/release-notes" Release history for Bugsee Android SDK 7.x. Looking for the previous major version? See the [6.x release notes](/sdk/android/v6/release-notes). See the [migration guide](/sdk/android/migration) when planning your upgrade from 6.x. +## 7.1.2 + +A patch release for native crash reporting. Crashes in the first moments of a launch — a window that +was previously uncovered — are now captured, and crashes that kill the app before it can report are +delivered on the next start. + +- **Native crashes are captured from the very start of the first launch.** After an install or an + update, the SDK needs a moment to prepare its out-of-process native crash handler, and a crash + during that window went unreported. Bugsee now arms an in-process handler immediately at startup, + so those crashes arrive with the faulting library, its build ID and a stack, and upgrades to the + full handler as soon as it is ready. This is the window that used to hide crashes in native + libraries an app loads early. + +- **Crashes during startup, and crash loops, are now reported.** If your app crashes before capture + is fully running — including a loop where it never stays alive long enough to send anything — the + report is exported and uploaded during the next launch, instead of being handed to background work + the app never survives to run. If the device is offline the report is kept and retried. + +- **Reports created before capture starts are no longer discarded.** A report produced in that early + window was assembled without the list of capture providers and then dropped as unprocessable, so + the crash never arrived at all. + +- **A damaged crash handler no longer disables native reporting.** If the helper Bugsee extracts is + incomplete, or cannot be executed on a particular device, that is now detected during startup and + the in-process handler is kept instead of arming one that cannot run. Previously the combination + looked healthy and produced an empty report. + +- **Steadier crash handling.** The code that runs inside a crash no longer depends on library + functions that carry no guarantee of being safe there, and a race between arming the handler and a + crash arriving on another thread has been closed. Either could previously cost you the report. + +- **Optional libraries are no longer loaded merely to detect them.** Bugsee now checks whether + Material Components, AndroidX or `androidx.fragment` are present without initializing their + classes, so an app that never uses fragments never loads one on Bugsee's behalf. + +- **`addSecureView()` and `removeSecureView()` now take `Object`.** One overload previously took + `androidx.fragment.app.Fragment`. Passing a fragment still works exactly as before, and behavior is + unchanged when `androidx.fragment` is on the classpath. This removes the last non-platform type + from Bugsee's public API, which matters for hosts that inspect its methods reflectively — Unity + bindings in particular. + + :::note + Because the method signature changed, rebuild your app against 7.1.2 rather than dropping the new + AAR onto an existing build. No source changes are required. + ::: + ## 7.1.1 A patch release covering dependencies and WebView privacy. From 80879d4c600f32002ecbdfffc47ee1ebb3518af2 Mon Sep 17 00:00:00 2001 From: Alexey Karimov Date: Thu, 20 Aug 2026 11:45:06 +0500 Subject: [PATCH 2/2] docs(android): drop the WebView bridge note from 7.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The bridge authentication is inert until the matching JavaScript package ships, so the entry described behavior nobody can observe — and pointed readers at a "matching Bugsee JavaScript SDK" that is not out yet. Removes the bullet and the "and WebView privacy" half of the summary line above it, which would otherwise promise a change the entry no longer makes. Both this and 7.1.2 can document the work once it is live. Change-Id: Iceb7b9f8d8a551a7fe0fb6110310cef0c51be0e1 --- docs/sdk/android/release-notes.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/docs/sdk/android/release-notes.md b/docs/sdk/android/release-notes.md index b1d06f0..1030a76 100644 --- a/docs/sdk/android/release-notes.md +++ b/docs/sdk/android/release-notes.md @@ -55,7 +55,7 @@ delivered on the next start. ## 7.1.1 -A patch release covering dependencies and WebView privacy. +A patch release covering dependencies. - **Bugsee no longer adds the Kotlin standard library to your app.** Previously every project that included Bugsee picked it up, even apps written entirely in Java. It is now gone from the core SDK @@ -67,11 +67,6 @@ A patch release covering dependencies and WebView privacy. `org.jetbrains:annotations` indirectly, declare them yourself. Projects that already use Kotlin are unaffected. ::: -- **The WebView bridge is protected from page scripts.** Scripts running inside an instrumented - WebView could previously pause capture or stop the SDK. Bugsee now verifies that control messages - come from its own JavaScript SDK and ignores the rest. Requires the matching Bugsee JavaScript - SDK; older combinations continue to work unchanged. - ## 7.1.0 A feature and hardening release. WebSocket traffic is now captured, crash / ANR / exit reports carry