feat: persist Remote Config last-known-good - #753
Closed
shameondev wants to merge 23 commits into
Closed
Conversation
Contributor
Author
|
Консолидировано в release-train PR (один PR на репозиторий). Ветка сохранена. |
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.
Outcome
Adds persistent Last Known Good (LKG) delivery for Remote Configs so a process restart plus transient API/network failure returns the last valid response before falling back to the bundled file. Also exposes durable
frozenassignment provenance and serializes user-scope changes so late identify/logout/restore/launch responses cannot cross user boundaries.Stacked on #752 so the release contains both persistent fallback and restored TLS certificate/hostname verification.
Reliability contract
launchingFinishedfalse until every concurrent launch ticket terminates and forward the final terminal error when releasing queued workQONRemoteConfigurationAssignmentTypeFrozen = 2, preserving Unknown for future values and hardening malformed source/group parsingVerification
git diff --checkFull XCTest runs in GitHub CI; the local host has Command Line Tools only, without the Xcode platform SDK.
Release fence
Configurator type-3 writes remain disabled until this SDK and the corresponding Android/Sandwich/wrapper releases are in the compatibility matrix.