initialization errors aren't always surfaced

Question

initialization errors aren't always surfaced

Closed this issue 2 years ago · 6 comments

This issue was originally filed by @martinmckenna when the React SDK code was still part of the js-client-sdk repository. The original issue description and discussion is here.

Summary: in the specific case where an environment ID was not provided, the underlying JS SDK will fail to initialize but this type of failure is not communicated to the React SDK, so it will hang.

The original issue also mentioned the possibility of an existing environment ID becoming invalid so that LD would return a 401 or 403 error. We believe that in this case the React SDK will notice the error, but we should verify that.

Answer 1 · 2019-11-04T21:55:12.000Z

[tracked internally as 55120]

Answer 2 · 2022-05-15T09:46:19.000Z

Any updates on this issue?

Answer 3 · 2022-06-23T20:24:42.000Z

Hello Launch Darkly team! Also wondering if there are updates on this issue? Hoping to have a React-based way of identifying an ldClient initialization error and being able to retry connecting to LD

Answer 4 · 2022-08-31T16:13:17.000Z

@Lukortech @Jshollow A solution for this went out in 2.27.0, take a look and see if it suits your needs. We added a new hook that will surface initialization failures, read useLDClientError.

Answer 5 · 2022-08-31T16:36:03.000Z

@Lukortech @Jshollow A solution for this went out in 2.27.0, take a look and see if it suits your needs. We added a new hook that will surface initialization failures, read useLDClientError.

Thanks for the mention, I am not a part of active team working with use of this sdk but I will try to see if It's good now.

Answer 6 · 2024-09-16T17:14:07.000Z

@XieX I could not see any references on how to use useLDClientError