From bfc7aa184748bcee54fa4232f246713e69e53871 Mon Sep 17 00:00:00 2001 From: tore-statsig <74584483+tore-statsig@users.noreply.github.com> Date: Wed, 21 Aug 2024 10:41:52 -0700 Subject: [PATCH 1/2] Update debugging.mdx --- docs/sdks/debugging.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/sdks/debugging.mdx b/docs/sdks/debugging.mdx index e16c1a4c2..964789e95 100644 --- a/docs/sdks/debugging.mdx +++ b/docs/sdks/debugging.mdx @@ -34,6 +34,8 @@ For client SDKs, these reasons for the value you are seeing can be: - `Error`: an unknown error has occured, and was logged to statsig servers - `Error:NoClient`: No client was found in StatsigContext. Likely a call to a Statsig hook outside of the StatsigProvider. (js-client-only) - `NetworkNotModified`: the network response came back, but the cached values were already up to date for this user +- `NoValues`: The sdk was initialized, but there were no values in the cache for the user (and nothing fetched from the network). Commonly caused by calling `initializeSync` rather than waiting for `initializeAsync` +- `Loading`: Initialize was called, but the sdk is still waiting for the network request to resolve with updated values. You should `await` initialization before issuing checks Newer versions of the sdk will contain two tags: one regarding the initialization state of the sdk, and the other qualifying different sources for that value. From 9526f34ab6e47674879c4fe352bed5aad0beaf5d Mon Sep 17 00:00:00 2001 From: tore-statsig <74584483+tore-statsig@users.noreply.github.com> Date: Thu, 7 Nov 2024 13:20:23 -0800 Subject: [PATCH 2/2] Update debugging.mdx merge client new + client and server new + server --- docs/sdks/debugging.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/sdks/debugging.mdx b/docs/sdks/debugging.mdx index 34528e28c..5ad12be99 100644 --- a/docs/sdks/debugging.mdx +++ b/docs/sdks/debugging.mdx @@ -48,8 +48,7 @@ When debugging why a certain user got a certain value, there are a number of too - `NetworkNotModified`: the network response came back, but the cached values were already up to date for this user - `NoValues`: The sdk was initialized, but there were no values in the cache for the user (and nothing fetched from the network). Commonly caused by calling `initializeSync` rather than waiting for `initializeAsync` - `Loading`: Initialize was called, but the sdk is still waiting for the network request to resolve with updated values. You should `await` initialization before issuing checks - - + Newer versions of the sdk will contain two tags: one regarding the initialization state of the sdk, and the other qualifying different sources for that value. So in addition to the reasons above, you may have: @@ -70,8 +69,7 @@ When debugging why a certain user got a certain value, there are a number of too - `LocalOverride`: from an override set locally on the SDK via an override API - `Unrecognized`: the sdk was initialized, but this config did not exist in the set of values - `Uninitialized`: the sdk was not yet successfully initialized - - + In newer server SDKs, the reasons will be a combination of initialization source and evaluation reason: **Initialization Source** - `Network`: fetched at SDK initialization time from the network