fix: report automatic rollbacks to the server on the next launch#4
Merged
fonkamloic merged 3 commits intoJun 12, 2026
Merged
Conversation
Crash-loop rollbacks happen before any Dart code runs, so they were invisible to server telemetry. The rollback now leaves a marker in the patch directory; on the next launch the SDK posts it to the client-error telemetry endpoint and clears it once the server confirms receipt (offline devices retry on a later launch).
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.
What
Automatic crash-loop rollbacks run before any Dart code, so the server (and the publisher dashboard) never learned about them — devices could be crash-looping and rolling back with zero telemetry.
How
initreads a marker file the rollback left in the patch directory and posts it to/api/v1/telemetry/client-erroraskind: auto_rollback(reason, patch version, boot count, timestamp).Pairs with an engine-side change that records the marker. Targets the checkpoint branch since it builds on the rc-series init flow.
Notes
dart format+dart analyzeclean (the 9 pre-existingavoid_printinfos on this branch are untouched).