feat: expose invalidateRemoteConfigsCache, bump sandwich to 7.12.0 (DEV-1236) - #466
Merged
SpertsyanKM merged 2 commits intoJul 30, 2026
Conversation
Bridges the new native cache invalidation API (android-sdk 9.7.0 / qonversion-ios-sdk 6.14.0 via sandwich 7.12.0). The method performs no network request and has no callback - it marks the remote configs cache stale so the next remoteConfig / remoteConfigList call fetches a fresh targeting evaluation. An in-flight remoteConfig load is re-issued once; an in-flight remoteConfigList completes with the evaluation it started with. Not needed after identify - the SDK invalidates automatically. Call after initialize. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- macOS is a declared platform with its own plugin copy (not a symlink): the missing invalidateRemoteConfigsCache case surfaced as a thrown MissingPluginException from a documented public API, and the stale macos podspec pin would have silently resolved a sandwich without the method. Both carried now, matching how every prior sandwich bump treated the macOS podspec. - Doc: state the retry degradation explicitly (a failed re-issue delivers the previously received evaluation instead of an error) and the pre-initialization consequence (throws on Android, no-op on iOS). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
SpertsyanKM
deleted the
kamo/dev-1236-sdk-iosandroid-obvyazki-refetch-rc-posle-identify-i-yavnii
branch
July 30, 2026 17:02
Merged
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.
B4 exposure from the Remote Config targeting review (dash-mono PR #674). Linear: DEV-1236. Exposes the new cache invalidation API released in android-sdk 9.7.0 / qonversion-ios-sdk 6.14.0, bridged by sandwich 7.12.0.
What changed
Qonversionexactly, so apps that also declare the nativeQonversionpod directly must move to 6.14.0.invalidateRemoteConfigsCache— a void no-callback pass-through to the native method. It performs no network request; it marks the remote configs cache stale so the nextremoteConfig/remoteConfigListcall fetches a fresh targeting evaluation. An in-flightremoteConfigload is re-issued once so its waiting calls receive a fresh evaluation (degrading to the superseded one if the retry fails); an in-flightremoteConfigListcompletes with the evaluation it started with. You do NOT need to call it afteridentify— the SDK invalidates on identity changes automatically. Call it after initialization (calling before initialization crashes on Android and no-ops on iOS, same as the other void bridges). Review round: the macOS platform copy (method channel case + podspec pin) is carried too — macOS has its own plugin file, not a symlink.Release notes for this wrapper (minor bump)
Source-breaking note for the release: the abstract
Qonversionclass gained a new required member — custom implementations and hand-written mocks must addinvalidateRemoteConfigsCache.New:
invalidateRemoteConfigsCache— invalidate the remote configs cache on demand (e.g. after setting a batch of user properties your targeting depends on).Native SDKs updated: Android 9.7.0, iOS 6.14.0 — automatic remote configs cache invalidation on same-uid
identify, never-worse re-issue of superseded in-flight loads, uncached bundled fallbacks with rate-limit tolerance (remote configs only).🤖 Generated with Claude Code
https://claude.ai/code/session_01Y4V5cx2SMU4VrfPntwfKJ9