SDK / Relay Proxy
- Common misconceptions about LaunchDarkly architecture
- How to improve implementation to be resilient to network failures
- How to use the SDK's "evaluation reasons" feature to troubleshoot flag evaluation
- Network troubleshooting checklist
- Troubleshooting Relay Proxy
- Anonymous users receive different flag evaluations when they return to your site
- Browser privacy settings block analytic events to LaunchDarkly
- Error "403: invalid SDK key" when initialising .NET SDK behind proxy or with NTLM authentication
- Error "429 Too Many Requests" API Rate Limit
- Error "CORS request did not succeed" on Firefox
- Error "Error in stream connection unable to find valid certification path to requested target" Java SDK
- Error "Exceeded event queue capacity. Increase capacity to avoid dropping events"
- Error "Initialization timeout exceeded for LaunchDarkly Client or an error occurred. Feature Flags may not yet be available."
- Error "Invalid Context Specified"
- Error "invalid_client" Apex SDK
- Error "invalid_client_id" Apex SDK
- Error "invalid_grant" Apex SDK
- Error "LaunchDarkly SDK already initialized" React Native SDK
- Error "LaunchDarklyFlagFetchError: network error"
- Error "ldclient.on('ready')" not firing JavaScript SDK
- Error "lua: error loading module 'launchdarkly_server_sdk'" Lua SDK
- Error "OutOfMemoryError" Java SDK
- Error "The located assembly's manifest definition does not match the assembly reference"
- Error "WARN: Error in stream connection (will retry): EOF"
- Error: "Data store returned error: ERR unencrypted connection is prohibited"
- Error: server-side streaming endpoints are non-functional
- How to analyze and reduce large SDK payloads
- How to avoid unknown flag variations when evaluating a flag
- How to bootstrap when serving from a CDN, not a backend
- How to check network connectivity using cURL