Complete React Native telemetry opt-out - #677
Draft
tiagocandido wants to merge 1 commit into
Draft
Conversation
tiagocandido
force-pushed
the
telemetry/android-integration
branch
from
August 19, 2026 13:02
c4a1ff0 to
f8749f0
Compare
tiagocandido
force-pushed
the
telemetry/react-native-integration
branch
from
August 19, 2026 13:02
31406fe to
4911668
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
getConfig()andsetConfig()round-tripping the same required boolean on iOS and AndroidValidation
Release dependency
The published native packages currently pinned by React Native do not yet expose the telemetry API, so full packaged native builds remain gated on telemetry-capable Swift and Android releases. The package pins are intentionally unchanged in this PR.