@launchdarkly/react-native-client-sdk 10.0.2 → 10.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,15 @@
4
4
 
5
5
 
6
6
 
7
+ ## [10.0.3](https://github.com/launchdarkly/js-core/compare/react-native-client-sdk-v10.0.2...react-native-client-sdk-v10.0.3) (2024-03-15)
8
+
9
+
10
+ ### Dependencies
11
+
12
+ * The following workspace dependencies were updated
13
+ * dependencies
14
+ * @launchdarkly/js-client-sdk-common bumped from 1.0.1 to 1.0.2
15
+
7
16
  ## [10.0.2](https://github.com/launchdarkly/js-core/compare/react-native-client-sdk-v10.0.1...react-native-client-sdk-v10.0.2) (2024-03-05)
8
17
 
9
18
 
package/README.md CHANGED
@@ -15,6 +15,19 @@ It is implemented purely in JS and supports Expo. Please consider updating your
15
15
 
16
16
  For more information, see the [complete reference guide for this SDK](https://docs.launchdarkly.com/sdk/client-side/react-native).
17
17
 
18
+ ## Known Android identify issue
19
+ On Android, Flipper interferes with the SDK's streaming connections. As a result the `identify` call never resolves. The long term solution is the removal of Flipper from react-native. The Facebook team are [working on this](https://reactnative.dev/blog/2023/12/06/0.73-debugging-improvements-stable-symlinks#flipper--react-native-integration).
20
+
21
+ In the meantime, we recommend one of these workarounds:
22
+
23
+ - If you are using Expo, you'll need to do a native build in release `expo run:android --variant release`.
24
+
25
+ - If you are using Expo and want to debug and hot reload, you'll need to do a native build in debug `expo run:android --variant debug` and then go to the `android` folder and manually find and remove all references to flipper. This is a [reported issue](https://github.com/facebook/flipper/issues/1326#issuecomment-652946496) in the Flipper repo.
26
+
27
+ - If you are using the expo-go app on Android, unfortunately there is no known easy way to disable Flipper in Expo Go. Please use one of two previous native build options.
28
+
29
+ - If you are not using Expo, go to the `android` folder and manually find and remove all references to flipper.
30
+
18
31
  ## Install
19
32
 
20
33
  ```shell
package/dist/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@launchdarkly/react-native-client-sdk",
3
- "version": "10.0.2",
3
+ "version": "10.0.3",
4
4
  "description": "React Native LaunchDarkly SDK",
5
5
  "homepage": "https://github.com/launchdarkly/js-core/tree/main/packages/sdk/react-native",
6
6
  "repository": {
@@ -43,7 +43,7 @@
43
43
  "react-native": "*"
44
44
  },
45
45
  "dependencies": {
46
- "@launchdarkly/js-client-sdk-common": "1.0.1",
46
+ "@launchdarkly/js-client-sdk-common": "1.0.2",
47
47
  "@react-native-async-storage/async-storage": "^1.21.0",
48
48
  "base64-js": "^1.5.1",
49
49
  "event-target-shim": "^6.0.2"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@launchdarkly/react-native-client-sdk",
3
- "version": "10.0.2",
3
+ "version": "10.0.3",
4
4
  "description": "React Native LaunchDarkly SDK",
5
5
  "homepage": "https://github.com/launchdarkly/js-core/tree/main/packages/sdk/react-native",
6
6
  "repository": {
@@ -43,7 +43,7 @@
43
43
  "react-native": "*"
44
44
  },
45
45
  "dependencies": {
46
- "@launchdarkly/js-client-sdk-common": "1.0.1",
46
+ "@launchdarkly/js-client-sdk-common": "1.0.2",
47
47
  "@react-native-async-storage/async-storage": "^1.21.0",
48
48
  "base64-js": "^1.5.1",
49
49
  "event-target-shim": "^6.0.2"