Repository navigation
Conversation
Telemetry is on unless the user turned it off; the consent sheet and the onboarding step are gone, and a stored opt-out is kept. A new build is reported on its first launch, and the daily check runs at launch, on foreground and from the scheduler, with a one-hour wait after a failed attempt. Installs that turned sharing off send a minimal daily check-in with the app version, build and a random install ID.
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.
Usage telemetry is on by default, the same way Trio does it. The consent sheet and the onboarding Privacy step are removed. Users who already chose No thanks or turned the toggle off keep that choice, since a stored false is always an explicit opt-out. Installs that have sharing off send only a minimal check-in once a day and after installing a new build. It carries the app version, build date, commit, a random install ID, what triggered it and the last failure category, and nothing about the device, settings or health data.
The first launch of a new build (version, build date or commit) sends at once, so the server gets an early signal of updates. Otherwise the daily check runs at cold launch, on foreground and from the task scheduler. After a failed attempt it waits an hour, which also stops the immediate refires that happened when a send failed. Each request includes the trigger reason and the previous failure category. The check-in also carries a random install ID that survives an IDFV reset. The privacy screen and the What's sent preview describe both modes.
This needs the matching lftelemetryapi change deployed first: the new unique key, the reason and install ID columns, and the /api/telemetry/anonymous endpoint.