Frequently Asked Questions

When you encounter the error statsigSDK> Event metadata is too large (max 4096). Some attributes may be stripped. in your logs, it indicates that the size of the metadata for a particular event has exceeded the maximum limit of 4096 characters when stringified. This limit is set by Statsig to ensure efficient data handling.

To resolve this issue, you should review the events you're logging and the associated metadata. You might be logging more information than necessary or there could be large data structures being included unintentionally. If you're unsure about what metadata is being sent, you can add debugging statements in your code to print out the metadata before it's sent to Statsig. This will help you identify any unusually large pieces of data. Once you've identified the cause, you can then modify your logging to reduce the size of the metadata. The goal is to log only the information that is necessary for your metrics and analyses.

When deploying to an environment in Statsig, if you encounter an issue where the RULE is always Default and the REASON is Unrecognized, it typically means that the SDK was initialized, but the config or feature gate you're trying to evaluate did not exist in the set of values. This could be due to a few reasons:

1. The feature gate or dynamic config you're trying to evaluate does not exist or is not correctly spelled in your code. Please double-check the spelling and case-sensitivity.

2. The SDK might not have been able to fetch the latest rules from the Statsig server. This could be due to a transient network issue. If so, restarting the client or server should fix it, or waiting for a server SDK to poll for updates (by default, every 10 seconds).

3. The Target App you added to the SDK key you are initializing with may not be set on the gate/config/experiment/layer you are checking in your application. If you are using target apps, be double check that the target application on the entity you are checking matches the target application on the SDK key.

4. The gate has no rules in it. Gates return false by default, so a gate with no rules always returns false. Checking a gate that does not exist also returns false. As an optimization, we've removed gates which do not exist from the payload to sdks. So you may see an "Unrecognized" check if the gate has no rules (and therefore returns false anyway)

In the event of encountering unexpected diagnostic results when evaluating a gate on React Native, despite the gate being set to 100% pass and Statsig being initialized, there are several potential causes to consider.

The "Uninitialized" status in evaluationDetails.reason can occur even after calling .initialize() and awaiting the result. This issue can be due to several reasons:

1. **Ad Blockers**: Ad blockers can interfere with the initialization network request, causing it to fail.

2. **Network Failures**: Any network issues that prevent the initialization network request from completing successfully can result in an "Uninitialized" status.

3. **Timeouts**: The statsig-js SDK applies a default 3-second timeout on the initialize request. This can lead to more frequent initialization timeouts on mobile clients where users may have slower connections.

If you encounter this issue, it's recommended to investigate the potential causes listed above. Check for the presence of ad blockers, network issues, and timeouts. This will help you identify the root cause and implement the appropriate solution.

If you're still experiencing issues, you can check the diagnostics tab for higher-level pass/fail/bucketing population sizes over time. For debugging specific checks, the logstream at the bottom is useful and shows both production and non-production exposures in near real-time. You can also use the Users tab to see historical evaluation results for a given ID.