26 September 2024 (v2.120)
ReachFive v2.120 introduces a few improvements and needed bug fixes.
We are happy to announce new releases of both our Android and iOS mobile SDKs.
We have introduced new Management API endpoints for fetching users by different ID types. As always, we made some general improvements and fixed a few items for you.
Mobile SDK releases
Alongside this release, we have released new versions of both our Android and iOS mobile SDKs, each containing exciting updates.
The Android 9.3.0 release includes new methods allowing you to manage trusted devices for Risk-based Authentication support.
You can also now start the stepup flow using the loginWithPassword method when MFA is required.
The iOS 7.1.0 release now supports native Sign in with Apple.
For more on this topic, see iOS use cases.
New Management API endpoints
We have created dedicated endpoints to fetch users more specifically by email, phone number, custom IDs, and external IDs.
This means, the previously deprecated /users/email/:email endpoint is available again.
The three new endpoints are:
-
GET user by external ID:
/users/external_id/:externalIdendpoint -
GET user by custom ID:
/users/custom_id/:customIdendpoint -
GET user by phone number:
/users/phone_number/:phoneNumberendpoint
General improvements
-
We updated the ReachFive Console Job related screens (such as Job reports and Job definitions) to display the Last updated column with specific date and time information instead of the general X days/months/years ago.
-
We’ve improved the labelling on the ReachFive Console so that when you select the fields to send in a Pub/Sub hook or webhook, it’s clear that Login Time (Deprecated - Use Date instead) is just an alias for Event - Date. Unless your setup explicitly requires Login Time, it’s best to use Event - Date.
Fixes
| Item | Fixed |
|---|---|
Some import jobs were taking longer than expected to import user profiles. |
✓ |
In some limited cases when a user was created, the |
✓ |