LaunchDarkly Client-Side SDK for React Native (7.0.0)

The default value is 3600000ms (1 hour).

The default value is 10000ms (10 seconds).

This setting is only used when running in iOS. In Android this setting is ignored.

The default value is false.

If this is true, the client will periodically poll for updates while in the background; if false, the SDK will not attempt to receive updates while the app is backgrounded.

The default value is false.

The default value is false (the SDK will not send mobile environment data).

The additional information will then be available through the client's LDClient.*VariationDetail methods. Since this increases the size of network requests, such information is not sent unless you set this option to true.

The client buffers up to this many events in memory before flushing. If the capacity is exceeded before the queue is flushed, events will be discarded. Increasing the capacity means that events are less likely to be discarded, at the cost of consuming more memory. Note that in regular usage flag evaluations do not produce individual events, only summary counts, so you only need a large capacity if you are generating a large number of click, pageview, or identify events (or if you are using the event debugger).

The default value is 100.

Most customers should use the default value.

The default value is 30000ms (30 seconds).

Set to true to make the SDK provide unique keys for anonymous contexts. Read more at https://launchdarkly.github.io/android-client-sdk/com/launchdarkly/sdk/android/LDConfig.Builder.html#generateAnonymousKeys(boolean).

The default is true.

This field is required as the React Native SDK will use this value to uniquely identify your LaunchDarkly account.

This can also be specified after the client has been created, using LDClient.setOffline().

The default value is false (the client will make network calls).

Most customers should use the default value.

The default value is 300000ms (5 min).

You can also specify this on a per-context basis with {@link LDContextMeta.privateAttributes}

If this is true, the client will always attempt to maintain a streaming connection; if false, it never will.

The default value is true.

Most customers should use the default value.

If this is true, flag settings will be fetched with a REPORT request including a JSON entity body with the context.

Otherwise (by default) a GET request will be issued with the context passed as a base64 URL-encoded path parameter.

Do not use unless advised by LaunchDarkly.

Kinds of errors include:

• 'CLIENT_NOT_READY': The client is not able to establish a connection to LaunchDarkly yet. If there is a persistent feature store, the store does not yet contain flag data.
• 'FLAG_NOT_FOUND': The flag key did not match any known flag.
• 'USER_NOT_SPECIFIED': The user object or user key was not provided.
• 'MALFORMED_FLAG': There was an internal inconsistency in the flag data. For example, a rule specified a nonexistent variation. This is an unusual condition that might require assistance from LaunchDarkly's Support team.
• 'WRONG_TYPE': The application code requested the flag value with a different data type than it actually is. For example, the code asked for a boolean when the flag type is actually a string.
• 'EXCEPTION': An unexpected error stopped flag evaluation. This could happen if you are using a persistent feature store and the database stops working. When this happens, the SDK always prints the specific error to the log.