Repository navigation
Fix sensor warmup, scan recovery, and live glucose updates - #35
Merged
Merged
Conversation
This was referenced Aug 15, 2026
shroominic
marked this pull request as ready for review
August 15, 2026 14:28
This was referenced Sep 1, 2026
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
Root causes
Warmup readings and operational latest-reading state were reused directly by presentation and export integrations. AiDEX history catch-up could also start during warmup and fail without a reliable resume path. Live notification glucose had been intentionally redacted for privacy, but there was no reviewed consent UI to enable it. Scan failures were flattened to text and older scans could mutate UI after retry or connection transitions.
User impact
Users no longer see misleading initial sensor values or raw exception types. Warmup and live-glucose notification behavior is explicit and recoverable. Lock-screen glucose remains private by default and requires informed opt-in; withdrawal removes sensitive surfaces even if preference persistence fails.
Validation
make tooling-checkmake format-check lint testmake build-webgit diff --checkLocal Android compilation is unavailable because this Mac has no Java runtime, and full iOS XCTest execution requires full Xcode. GitHub Actions is the authoritative native build/test gate for this PR.