19 October 2023 (v2.102)
ReachFive v2.102
now enables you to block unverified login requests, brings some SDK updates, introduces support for more Chinese language variations, and provides an update to our LINE social provider. We also made some other improvements. And as always, we fixed a few issues for you.
SDK updates
We made some updates to our SDKs in support of this release.
We added two new methods to our Core SDK which allow you to better manage trusted devices:
For a full list of methods, see our Core SDK.
Now, you need to add your GOOGLE_CLIENT_ID
to the Info.plist
file.
This is only applicable from our iOS SDK version 5.9.0
.
...
<key>GIDClientID</key>
<string>GOOGLE_CLIENT_ID</string> (1)
...
1 | This is your Google Client ID in standard format. For example, 1234567890-abcdefg.apps.googleusercontent.com . |
For more details, see our iOS SDK.
Chinese language support
We have added more variations of our support for Chinese including:
-
zh-CN
- People’s Republic of China Simplified Chinese -
zh-Hans
- Simplified Chinese -
zh-Hant
- Traditional Chinese -
zh-HK
- Hong Kong Traditional Chinese -
zh-MO
- Macao Traditional Chinese -
zh-SG
- Singapore Simplified Chinese -
zh-TW
- Taiwan Traditional Chinese
For a full list, see Supported languages.
LINE social provider updates
You can now configure your LINE social provider login to prompt users to add LINE friends directly in their consent screen or in a follow-up screen depending on the configuration. You handle the configuration directly in the ReachFive Console.
For more details, see Line Connect.
Other improvements
-
We improved the wording on errors for some customers.
-
We enhanced the mapping for Oracle Responsys for unknown users, and in the process, removed the need for the Folder Name and Object Name.
For more, see the Oracle Responsys section at Set up email provider.
-
You can now connect to the ReachFive Console with Ping Identity.
Fixes
Item | Fixed |
---|---|
Some customers were unable to user filters successfully when searching user events. |
✓ |
There was a minor issue related to roles when creating new users on the console. |
✓ |
There was a small issue using custom fields with the data type |
✓ |
A technical issue was causing some issue when exporting consent logs. |
✓ |