Report iPhone relay health without false offline states - #249
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
The app could report an iPhone relay as offline without a clear health model, retry path, or distinction from hosted/non-iPhone relay configurations.
Change
Add explicit healthy, stale, offline, and recovered relay states; retry/polling behavior; profile/setup status; and notification gating only for actual iPhone relays.
Validation
Focused tests pass for healthy, stale, offline, recovered, and non-iPhone/hosted gating. Targeted analyzer reports no errors.
Privacy and scope
Health events contain state and timing, not messages or credentials. This does not change composer annotations, CloudKit, or general reconnect transport semantics.