Add opt-in FaceTime session diagnostics - #247
Draft
Xare123 wants to merge 1 commit into
Draft
Conversation
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
1 participant
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.
Problem
FaceTime media/session failures are difficult to diagnose without exposing sensitive call data or enabling verbose capture for every user.
Change
Add a developer-only, explicit opt-in diagnostics switch and sanitized native session events. Disabling developer mode clears the opt-in.
Privacy
Diagnostics default off and omit names, handles, URLs, tokens, SDP, ICE credentials, console message contents, and media payloads.
Validation
Focused Dart contract tests pass: 4/4. A focused Kotlin gate test is included for native CI.
Non-goals
No automatic upload and no claim that diagnostics repair audio/video transport. This is independent of the FaceTime race-fix draft.