[LaunchDarkly] identify error: LaunchDarklyTimeoutError: identify timed out after 5 seconds on IOS

TL;DR

For "{ timeout: 10 }": issue launchdarkly/js-core#516 (closed, 32 comments): Describe the bug [LaunchDarkly] identify error: LaunchDarklyTimeoutError: identify timed out after 5 seconds To reproduce Use this component as a Provider ``` import { LDProvider, ReactNativeLDClient, AutoEnvAttributes, } from "@launchdarkly/react-native-client-sdk"; import { useEffect } from "react"; const LaunchDarklyProvider = ({ children }: PropsWithChildren): ReactNode => { const client = new ReactNativeLDClient(MOBILE_KEY, AutoEnvAttributes.Disabled);

{ timeout: 10 }

Steps

1. Issue launchdarkly/js-core#516 (closed, 32 comments): Describe the bug [LaunchDarkly] identify error: LaunchDarklyTimeoutError: identify timed out after 5 seconds To reproduce Use this component as a Provider ``` import { LDProvider, ReactNativeLDClient, AutoEnvAttributes, } from "@launchdarkly/react-native-client-sdk"; import { useEffect } from "react"; const LaunchDarklyProvider = ({ children }: PropsWithChildren): ReactNode => { const client = new ReactNativeLDClient(MOBILE_KEY, AutoEnvAttributes.Disabled);
2. The identify timeout is not a failed identify: the promise rejects, but the SDK keeps retrying in the background, so do not treat the timeout as an error. Practical steps from the thread:
3. Call identify only once per context change. One user found duplicate identify calls were their whole problem.
4. If you need more headroom, raise the identify timeout option (for example { timeout: 10 }) and catch the timeout instead of surfacing it.
5. If dev tooling or network interception (msw, BrowserStack logging, and similar) breaks SSE streaming, switch to polling: ldClient.setConnectionMode('polling').
6. This is expected SDK behavior per the maintainer, so the fix is in how you call and configure identify, not a version upgrade.

When to use

You are seeing this: The identify timeout is not a failed identify: the promise rejects, but the SDK keeps retrying in the background, so do not treat the timeout as an error. Use this skill when you run into "[LaunchDarkly] identify error: LaunchDarklyTimeoutError: identify timed out after 5 seconds on IOS".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In gh:launchdarkly/js-core#516 (LaunchDarkly), the issue reported was: Issue launchdarkly/js-core#516 (closed, 32 comments): Describe the bug [LaunchDarkly] identify error: LaunchDarklyTimeoutError: identify timed out after 5 seconds To reproduce Use this component as a Provider ``` import { LDProvider, ReactNativeLDClient, AutoEnvAttributes, } from "@launchdarkly/react-native-client-sdk"; import { useEffect } from "react"; const LaunchDarklyProvider = ({ children }: PropsWithChildren): ReactNode => { const client = new ReactNativeLDClient(MOBILE_KEY, AutoEnvAttributes.Disabled); The verified resolution from the thread: The identify timeout is not a failed identify: the promise rejects, but the SDK keeps retrying in the background, so do not treat the timeout as an error. Practical steps from the thread:

1. Call identify only once per context change. One user found duplicate identify calls were their whole problem.
2. If you need more headroom, raise the identify timeout option (for example { timeout: 10 }) and catch the timeout instead of surfacing it.
3. If dev tooling or network interception (msw, BrowserStack logging, and similar) breaks SSE streaming, switch to polling: ldClient.setConnectionMode('polling').

This is expected SDK behavior per the maintainer, so the fix is in how you call and configure identify, not a version upgrade. Source: mount the host path https at container path //github.com/launchdarkly/js-core/issues/516