From 6364e92ee60046d5152c345077df7069fbebeae5 Mon Sep 17 00:00:00 2001 From: Denis Sheikherev Date: Mon, 2 Nov 2026 12:43:56 +0700 Subject: [PATCH 1/2] docs(ios): drop the data encryption mentions from the 7.0.0 notes and migration guide Data encryption was an experimental option that was never announced, so the docs should not point at it. Remove "the data encryption option and BugseeDataEncryptionMode are no longer in the public headers" from the 7.0.0 release notes, and BugseeDataEncryptionMode from the migration guide's "no longer public" list. Co-Authored-By: Claude Opus 5.5 Change-Id: I76486df392c6306f8a3106c88542347c95306249 --- docs/sdk/ios/migration.mdx | 3 +-- docs/sdk/ios/release-notes.md | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/sdk/ios/migration.mdx b/docs/sdk/ios/migration.mdx index c98afd91..cbb9d25a 100644 --- a/docs/sdk/ios/migration.mdx +++ b/docs/sdk/ios/migration.mdx @@ -581,8 +581,7 @@ These still exist but changed shape; each shows up as a build error where it mat | `BugseeLogEvent.timestamp` is writable | Read-only | | `BugseeOptions.maxNetworkBodySize` below 20480 is raised to 20480 | Used as given; `0` captures no bodies | -`BugseeDataEncryptionMode`, `BugseeAdditionalDataCaptureBlock` and -`BugseeLogger.reactNativeLogger` are no longer public. +`BugseeAdditionalDataCaptureBlock` and `BugseeLogger.reactNativeLogger` are no longer public. ### 4.8 Lifecycle events diff --git a/docs/sdk/ios/release-notes.md b/docs/sdk/ios/release-notes.md index 6821b26a..9e9b3a93 100644 --- a/docs/sdk/ios/release-notes.md +++ b/docs/sdk/ios/release-notes.md @@ -25,8 +25,7 @@ changed since 7.0.0-beta7. `registerExt:`, `BugseeCommunicationManager`, `BGSOptionsContainer` and the `BGSLifecycleEvent*` names. App code keeps `Bugsee.ext(_:)`. Headers that were never app API, such as `BGSContracts.h`, and the unprefixed protocol and type aliases they declared, - are no longer public. `BGSAppearance` is removed (use `+[Bugsee getAppearance]`), and the data - encryption option and `BugseeDataEncryptionMode` are no longer in the public headers. + are no longer public. `BGSAppearance` is removed (use `+[Bugsee getAppearance]`). - `BugseeOptionConfigMaxDataSize` now limits the disk space taken by reports waiting to be sent, and its default rises from 50 to 150 MB. Past the limit the oldest reports are deleted whole: errors first, then bug reports, then crashes. The newest crash is always kept. From afbc2c5f1a2a7743076133ca9798e6d16c175063 Mon Sep 17 00:00:00 2001 From: Denis Sheikherev Date: Mon, 2 Nov 2026 13:40:19 +0700 Subject: [PATCH 2/2] docs(react-native): drop the data-encryption option from the configuration table Same reason as the iOS change: data encryption was an experimental, unannounced feature, so the docs stop mentioning it without a note. Co-Authored-By: Claude Opus 5.5 Change-Id: I5e6684fcc11a5620dd2d87673d72dd8496d19c88 --- docs/sdk/react_native/configuration.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/sdk/react_native/configuration.mdx b/docs/sdk/react_native/configuration.mdx index 102df2db..745c3832 100644 --- a/docs/sdk/react_native/configuration.mdx +++ b/docs/sdk/react_native/configuration.mdx @@ -235,7 +235,6 @@ Some keys are accepted by one SDK only; the other SDK does not recognize them. ` | `com.bugsee.option.capture.websocket` | boolean | `true` | Record WebSocket traffic; see [Network events](/sdk/react_native/network#websocket-traffic). | | `com.bugsee.option.config.build-target` | string | none | Build target name, sent with reports. | | `com.bugsee.option.config.build-type` | string | none | Build type, such as `debug` or `release`, sent with reports. | -| `com.bugsee.option.config.data-encryption` | number | `0` | Encryption of the collected data: `0` none, `1` on device (keys kept in the Secure Enclave), `2` end to end (decrypted only on the server, so some features, such as the video preview, are missing). The package exports no constants for it. | | `com.bugsee.option.detect.crash.fill_empty_exception_stacks` | boolean | `false` | Fill in the stack of an uncaught `NSException` that has none from the crashing thread. This can change how crashes are grouped. | | `com.bugsee.option.detect.crash.swift_async_stacktraces` | boolean | `true` | Stitch Swift async frames into the stacks of C++ exceptions. | | `com.bugsee.option.reporting.ui.style` | number | `3` | Style of the report UI: `0` Light, `1` Dusk, `2` based on the status bar, `3` the system style. The package exports no constants for it. |