[dsheikherev]

Summary

Data encryption was an experimental feature that was never announced. Since it was never public, we remove it from the docs silently: no release-note entry or migration note says it is gone, and the pages simply stop mentioning it.

• release-notes.md (7.0.0): removed "and the data encryption option and BugseeDataEncryptionMode are no longer in the public headers".
• migration.mdx (§4.7): removed BugseeDataEncryptionMode from the "no longer public" list. BugseeAdditionalDataCaptureBlock and BugseeLogger.reactNativeLogger stay.
• React Native configuration.mdx: removed the com.bugsee.option.config.data-encryption row, which described the modes in detail.

There are no other mentions in the SDK pages. The 7.x agent skill still greps for the raw 6.x "DataEncryption" option string so that an app already using it gets migrated; that is left as is.

Test plan

• cspell: 0 issues
• npm run build: success

🤖 Generated with Claude Code

[coderabbitai]

Important

• Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 15d194d4-fb1e-42a2-bc7a-58ea747b1821

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[claude]

Claude finished @dsheikherev's task in 14s —— View job

---

Review of PR #128

• Read the diff against origin/main
• Grep the docs for remaining mentions of data encryption
• Post the review

Findings

None. I found no bugs or risks and posted no inline comments.

• Removals are clean. Both edits drop the encryption wording and leave the sentences grammatical.
  • docs/sdk/ios/release-notes.md (7.0.0): the sentence now ends at "BGSAppearance is removed (use +[Bugsee getAppearance])."
  • docs/sdk/ios/migration.mdx §4.7: the line now reads "BugseeAdditionalDataCaptureBlock and BugseeLogger.reactNativeLogger are no longer public." It still renders as a plain paragraph after the table.
• Nothing else mentions it. I grepped docs/, src/, static/ and sidebars.ts for DataEncryption and data encryption. The only hit is the "DataEncryption" string in the option-key grep in docs/ai/agent-skills/sdk/ios/v7/SKILL.md:70. That file is generated from bugsee-for-ai and must not be edited here, as the PR description notes.
• Migration guidance is unaffected. The skill still greps for the raw 6.x option string, so an app using it still gets flagged. The migration page now says nothing about it, so a user who set DataEncryption in 6.x gets no docs hint that the option is gone. That fits the "never announced" intent, and the skill covers the case.
• No other files need changes. No sidebar, link or anchor changes are involved.
• Checks. I did not run cspell or the build. The PR description reports both passing, and a wording-only removal is very unlikely to affect either.

Summary

1. Overall risk: Low.
2. Merge recommendation: Approve and merge. Merging into main triggers the auto-deploy, which is the intended outcome for a docs change.
3. Most important issues to fix: None.
4. Positives:
   • The change is tightly scoped.
   • The PR description explains why the generated skill file is left alone.
   • The rest of the sentences and lists were kept intact.
     · Branch: docs/ios-drop-encryption-mentions

[claude]

Claude finished @dsheikherev's task in 17s —— View job

---

Review of PR #128 (re-run after the new commit)

• Read the diff against origin/main, now including the React Native commit
• Grep docs/, src/ and static/ for leftover data-encryption mentions
• Post the review

Findings

None. I posted no inline comments.

New commit (afbc2c5, React Native configuration.mdx):

• It removes the com.bugsee.option.config.data-encryption row from the options table.
• The rows around it (config.build-type and detect.crash.fill_empty_exception_stacks) are untouched, so the table markup is intact.
• A grep for data-encryption and DataEncryption across docs/, static/ and src/ finds only the "DataEncryption" string in the option-key grep in docs/ai/agent-skills/sdk/ios/v7/SKILL.md:70. That file is generated from bugsee-for-ai and must not be edited here, so leaving it is correct.
• The other "encrypt" hits are unrelated: the Android release note on malformed inputs and the CLI release note about TLS.
• Nothing links to the removed row or its anchor. The options table has no row-level anchors.

Earlier commit (iOS release notes and migration guide): Those edits are the ones I reviewed before, and nothing has changed in them. Both sentences are still grammatical.

Behaviour to be aware of: Nothing in the docs now tells a user who set the encryption option in 6.x, or in the React Native iOS options, that it has gone. This matches the "never announced, remove silently" intent in the description. The iOS 7 agent skill still flags the raw option string, so that case is covered for agent-driven migrations.

Checks: I did not run cspell or the build. The PR description reports both passing. They ran before the React Native commit, so confirm CI is green on the latest push. A table-row deletion is very unlikely to affect either.

Summary

1. Overall risk: Low.
2. Merge recommendation: Approve and merge. Merging into main triggers the production deploy, which is the intended outcome for a docs change.
3. Most important issues to fix: None.
4. Positives:
   • Scope is tight and consistent across iOS and React Native.
   • The generated skill file is correctly left alone.
   • The PR description explains why.

Optional: the PR description mentions only the two iOS files, so add a line about the React Native table row for reviewers.
· Branch: docs/ios-drop-encryption-mentions