Skip to content

FMEPRD-186 Update Mobile and Web SDK: Does the SDK Cache Expire? FAQ #10591

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

FMEPRD-186 Update Mobile and Web SDK: Does the SDK Cache Expire? FAQ #10591

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion ...ture/faqs-client-side-sdks/ios-android-browser-sdk-does-the-sdk-cache-expire.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,4 +14,9 @@ The Split mobile (iOS and Android) and JavaScript Browser SDKs download a local

## Answer

The SDK will consider the cache stale if it hasn't been updated for 90 days. In such case it will issue a full download of FME definitions. This is an unlikely scenario since the SDK is continuously synching changes from the Harness FME servers and updating the cache.
- For the JavaScript SDK, version 11.2.0 introduces a default cache expiration period of 10 days, which is configurable using the `LOCALSTORAGE` setting. After expiration, the SDK will refresh the cache from scratch.
- For the Browser SDK, version 1.2.0 introduces a default cache expiration period of 10 days, which is configurable using the `InLocalStorage` setting. For more information, see [Configuring LocalStorage cache for the SDK](/docs/feature-management-experimentation/sdks-and-infrastructure/client-side-sdks/browser-sdk#configuring-localstorage-cache-for-the-sdk).
- For the Android SDK, version 5.3.0 introduces a default cache expiration period of 10 days, which is configurable using the `rolloutCacheConfiguration` setting. After expiration, the SDK will refresh the cache from scratch.
- For the iOS SDK, version 3.3.0 introduces a default cache expiration period of 10 days, which is configurable using the `rolloutCacheConfiguration` setting. After expiration, the SDK will refresh the cache from scratch.

All SDKs continue to store impressions and events for up to 90 days, after which the cache is considered stale and may be purged.