You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Fixes an issue where react native components that use safe-area-context or react-navigation throw an error because the sdk's components try and use its own local node_modules instead of the consumer's project.
6
+
1
7
## 1.3.20
8
+
2
9
## Fixes
10
+
3
11
- Fixes an issue where the iOS SDK incorrectly targeted the latest minor version instead of a fixed version, potentially causing breaking changes.
4
12
5
13
## 1.3.19
14
+
6
15
## Updates
16
+
7
17
- updates to RN version 0.68.0 to address various security vulnerabilities
8
18
9
19
## 1.3.18
20
+
10
21
## Updates
22
+
11
23
- adds user id login for sample apps
12
24
- version mapping to newest native SDK versions
13
25
- updates versions of various package dependencies
14
26
15
27
## 1.3.17
28
+
16
29
## Fixed
30
+
17
31
- Fixes a specific Android issue where apps could crash due to EncryptedSharedPreference being null.
18
32
19
33
## 1.3.16
34
+
20
35
## Updates
21
36
22
37
This release allows you to use projects hosted on Iterable's EU data center. If your project is hosted on Iterable's [European data center (EUDC)](https://support.iterable.com/hc/articles/17572750887444), configure the SDK to use Iterable's EU-based API endpoints:
@@ -25,54 +40,63 @@ This release allows you to use projects hosted on Iterable's EU data center. If
25
40
constconfig=newIterableConfig();
26
41
// ... other configuration options ...
27
42
config.dataRegion=IterableDataRegion.EU;
28
-
Iterable.initialize('<YOUR_API_KEY>', config);
43
+
Iterable.initialize("<YOUR_API_KEY>", config);
29
44
```
30
45
31
46
## Fixed
47
+
32
48
- Addressed push notification deep linking issues on Android where the app would restart instead of resuming the last activity upon being backgrounded.
33
49
- Resolves an additional push notification problem on Android wherein the customActionHandler and urlHandler were not being invoked in specific scenarios, as documented in issue #470. (Credit to @tnortman-jabra for the report and the fix)
34
50
35
51
## 1.3.15
52
+
36
53
## Updates
54
+
37
55
- Resolves Android build issues caused in 1.3.14
38
56
- Fixes a specific Android issue where custom action handlers were not invoked when tapping on push notification when the app is in background.
39
57
40
58
## 1.3.14
59
+
41
60
> **Warning**
42
61
> This version causes build failure on Android. Please use 1.3.15 which fixes this issue.
62
+
43
63
## updates
64
+
44
65
- updates `Iterable.setEmail` and `Iterable.setUserId` to take in null parameter type
45
66
- fixes `Iterable.updateUser` on the Android side to merge nested objects in the user profile when `mergeNestedObjects` is set to true
46
67
47
68
## 1.3.9
69
+
48
70
### Added
49
71
50
-
[Version 1.3.9](https://github.com/Iterable/react-native-sdk/releases/tag/1.3.9) of Iterable's React Native SDK makes it possible for iOS apps to store in- app messages in memory, rather than in an unencrypted local file. ([Version 1.3.7](https://github.com/Iterable/react-native-sdk/releases/tag/1.3.7) added this same support for Android.)
72
+
[Version 1.3.9](https://github.com/Iterable/react-native-sdk/releases/tag/1.3.9) of Iterable's React Native SDK makes it possible for iOS apps to store in- app messages in memory, rather than in an unencrypted local file. ([Version 1.3.7](https://github.com/Iterable/react-native-sdk/releases/tag/1.3.7) added this same support for Android.)
51
73
52
74
To store in-app messages in memory on both iOS and Android, set `useInMemoryStorageForInApps` to `true`:
53
75
54
76
```javascript
55
77
constconfig=newIterableConfig();
56
78
// ... other configuration options ...
57
79
config.useInMemoryStorageForInApps=true;
58
-
Iterable.initialize('<YOUR_API_KEY>', config);
80
+
Iterable.initialize("<YOUR_API_KEY>", config);
59
81
```
60
82
61
-
This release deprecates `androidSdkUseInMemoryStorageForInApps`, which was introduced in version 1.3.7, and replaces it with `useInMemoryStorageForInApps`. However, for now:
83
+
This release deprecates `androidSdkUseInMemoryStorageForInApps`, which was introduced in version 1.3.7, and replaces it with `useInMemoryStorageForInApps`. However, for now:
62
84
63
-
- Android apps store in-app messages in memory if `useInMemoryStorageForInApps` is `true`, `androidSdkUseInMemoryStorageForInApps` is `true`, or if both are `true`.
85
+
- Android apps store in-app messages in memory if `useInMemoryStorageForInApps` is `true`, `androidSdkUseInMemoryStorageForInApps` is `true`, or if both are `true`.
64
86
65
87
- iOS apps store in-app messages in memory if `useInMemoryStorageForInApps` is `true`. `androidSdkUseInMemoryStorageForInApps` does not affect iOS apps.
66
88
67
89
When you can, please update your apps to use `useInMemoryStorageForInApps` instead of `androidSdkUseInMemoryStorageForInApps`.
68
90
69
-
When users upgrade to a version of your iOS or Android app that uses this version of the SDK (or higher), and they've enabled in-app memory storage, the local file used for in-app message storage (if it already exists) is deleted. However, no data is lost.
91
+
When users upgrade to a version of your iOS or Android app that uses this version of the SDK (or higher), and they've enabled in-app memory storage, the local file used for in-app message storage (if it already exists) is deleted. However, no data is lost.
70
92
71
93
## 1.3.7
94
+
72
95
Starting with this release, as a privacy enhancement, Iterable’s React Native
73
96
SDK encrypts some data stored at rest.
74
97
75
98
#### iOS updates
99
+
76
100
In iOS apps, Iterable's React Native SDK now encrypts the following fields when
77
101
storing them at rest:
78
102
@@ -86,7 +110,7 @@ storing them at rest:
86
110
messages at rest—before or after this update.)
87
111
88
112
When a user upgrades to a version of your app that uses this version of the SDK
89
-
(or higher), the fields shown above are encrypted. No data that's already stored
113
+
(or higher), the fields shown above are encrypted. No data that's already stored
90
114
is lost.
91
115
92
116
For more information about this encryption in iOS, examine the source code for
@@ -96,10 +120,12 @@ Iterable's iOS SDK (upon which the React Native SDK relies):
This feature saves a local copy of events triggered in your app while the device is offline (up to 1000 events). When a connection is re-established and your app is in the foreground, the events will be sent to Iterable.
161
193
Offline events processing is off by default, and we're rolling it out on a customer-by-customer basis. After you start using this version of the SDK, we'll send you a message before we enable the feature on your account (unfortunately, we can't give you an exact timeline for when this will happen). If you have any questions, talk to your Iterable customer success manager.
162
194
To use this feature, you must follow the SDK [upgrade instructions](#upgrade-instructions-for-version-1-1-0).
195
+
163
196
#### Updated
197
+
164
198
- New properties on the `IterableCommerceItem` class
165
199
The `IterableCommerceItem` class (which you can pass to the `trackPurchase` method on the `Iterable` class) now includes additional properties (all optional):
166
200
-`sku` (string) - The item's SKU
167
201
-`description` (string) - A description of the item
168
202
-`url` (string) - A URL associated with the item
169
203
-`imageUrl` (string) - A URL that points to an image of the item
170
204
-`categories` (string) - Categories to associate with the item
205
+
171
206
#### Upgrade instructions for version 1.1.0
207
+
172
208
To use this version of Iterable's React Native SDK, you'll need to update your native Android application's `Application` class:
209
+
173
210
- Add this import:
174
211
```java
175
212
importcom.iterable.iterableapi.IterableApi;
176
213
```
177
214
- At the end of the `onCreate` method, add this line of code:
0 commit comments