Upgrade async storage to v2

[kostyazgara]

Describe the bug
The SDK is using an outdated async storage lib that creates an ambiguous situation when need to use async storage lib in the project.

To reproduce
Install launchdarkly SDK version 10.10.5 and async storage 2.2.0

Expected behavior
LaunchDarkly SDK must use the latest version of async storage lib so that I can supress warnings from npx expo-doctor

Logs
Here is a result of running npx expo-doctor

Your project contains duplicate native module dependencies, which should be de-duplicated.
Native builds may only contain one version of any given native module, and having multiple versions of a single Native module installed may lead to unexpected build errors.
Found duplicates for @react-native-async-storage/async-storage:
  ├─ @react-native-async-storage/async-storage@2.2.0 (at: node_modules/@react-native-async-storage/async-storage)
  └─ @react-native-async-storage/async-storage@1.24.0 (at: node_modules/@launchdarkly/react-native-client-sdk/node_modules/@react-native-async-storage/async-storage)

SDK version
10.10.5

Language version, developer tools

OS/platform

• MacOS 15
• Node.JS 22
• Expo 54
• React Native 0.81

Additional context

[kinyoklion]

Hello @kostyazgara,

Thank you for the report. Are you experiencing any build or functionality errors/issues, or just the warning?

Thank you,
Ryan

[kostyazgara]

To be candid, I am unable to provide a definitive answer to this question. This issue manifested during the process of updating my Expo application to version 54, necessitating the upgrade of the async local storage v2 package. While I encountered other issues that compelled me to halt the upgrade and ascertain whether there were any problems, the Expo Doctor prompted me to upgrade the async local storage to version 2, as it was a requirement for Expo version 54. Therefore, I posit that this issue is related to build errors, as the absence of the upgrade prevents me from proceeding to the next major Expo version.

[kinyoklion]

It looks like the API itself didn't change, so the SDK should work with 2, just some internals changed that affect the supported RN version.

So you likely could use resolutions to resolve this to only have the one version.

We'll have to check minimum version support before we update, but it seems likely we can.

Thank you,
Ryan

[abarker-launchdarkly]

@kostyazgara React Native Client SDK v10.11.0 has been released to address this issue.