feat: expose resolve storage status - #268
Merged
Merged
Conversation
nicklasl
marked this pull request as ready for review
September 10, 2026 13:43
nicklasl
requested review from
andreas-karlsson,
fabriziodemaria,
mfranberg and
vahidlazio
as code owners
September 10, 2026 13:43
vahidlazio
approved these changes
Sep 10, 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
2 participants
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.
Applications can now choose an initialization strategy based on cached resolution age, using empty/fresh/stale status or custom checks that inspect the stored context. Mirrors spotify/confidence-sdk-android#261.
Successful fetches persist a timestamp atomically with the resolution. Legacy caches with no timestamp report stale; failed fetches preserve the previous timestamp. Includes usage examples and the public API snapshot.
Validation: 244 package tests and 201 iOS tests passed; SwiftLint passed. watchOS verification was blocked by the missing Xcode platform.