Non-breaking change.
When will this feature be available?
This feature is already available to Futurae Android and iOS SDKs customers that integrate the SDKs version 2.2.0 and beyond.
What is this feature about?
We are excited to announce that the Futurae mobile SDKs now support enrollment using the activation short code returned by the Futurae Auth API’s Enroll Mobile Device endpoints. This enhancement aims to provide users with increased flexibility and convenience during the enrollment process for customers integrating the Futurae mobile SDKs.
This enhancement aims to provide users with increased flexibility and convenience
Why is this important?
The short code support feature provides an alternative method for users to activate their mobile devices manually. In situations where scanning a QR code is not possible, or a user's camera is not functioning properly, as a fallback option, the short activation code can be manually entered by users in the app. This added flexibility ensures a seamless and reliable device activation experience for all users.
How to integrate this feature?
To utilize this functionality, simply include the short_code parameter when calling the Enroll Mobile Devices endpoints and set its value to true. This will ensure that a short activation code is included in the response payload, alongside the QR code and URIs. Users in the SDK app can then manually enter the short activation code for device activation.
To use this feature, it’s necessary to update the Android and iOS SDK versions to v2.2.0 or higher. Please refer to the following releases:
After updating the SDK version, you can find specific guidance on how to utilize the short code feature within your mobile apps in the documentation below:
Android SDK Enroll with activation shortcode
iOS SDK Enroll with activation shortcode
Does this change have any impact on my Futurae API integration?
This change has no impact on existing Futurae API or SDK integrations.
For any questions, please contact our support at support@futurae.com.
Comments
0 comments
Article is closed for comments.