Deprecations and API removal notices
Deprecated endpoints now removed
As previously announced, the endpoints that have been deprecated for several years have now been removed from the Digipass SDK.
Removed from the Java library
Removed endpoint | Equivalent endpoint to use instead |
|---|---|
|
|
|
|
|
|
|
|
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
|
|
Removed from the C library
Removed endpoint | Equivalent endpoint to use instead |
|---|---|
|
|
|
|
|
|
|
|
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
| N/A Digipass Plus features are no longer supported. |
|
|
DP4C API removed
The DP4C API has been removed entirely. This includes the following endpoints:
Removed endpoint | Equivalent endpoint to use instead |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DPSDK_GetDigipassProperty |
|
|
|
|
|
|
| N/A This feature is no longer supported. |
| N/A This feature is no longer supported. |
|
|
|
|
|
|
| N/A This feature is no longer supported. |
|
|
Client score-related APIs
All APIs related to the client score are marked as deprecated and will be removed in a future release.
Embedded-based methods
All Embedded-based methods are marked as deprecated and will be removed in a future release.
New features and enhancements
Android
Maven-based integration
The SDK artifact is now delivered as a local Maven repository, in addition to the previously published standalone aar artifact, and the package now also includes a documentation jar file. For more information, see Maven-based integration.
iOS
Prepare sample application for iOS 27
The sample application has been updated to adopt the UIKit scene-based application lifecycle which is required for apps to be built with iOS 27 and later. For more information, refer to the iOS documentation and iOS & iPadOS 27 Release Notes.
Enhanced error lookup
The technical documentation provided in the product package now includes the numeric value of each error code (DigipassSDKErrorCodes), making error lookup easier.
New password validation method
A new method for password validation has been added, validatePasswordWithFingerprint which now returns a new type DigipassSDKValidationResponse and deprecate the existing one, DigipassSDK.validatePassword , which returns DigipassSDKGenericResponse.
// New:
+ (DigipassSDKValidationResponse * _Nullable)validatePasswordWithFingerprint:(NSString * _Nullable)platformFingerprint
staticVector:(NSData *)staticVector
dynamicVector:(NSData *)dynamicVector
password:(char * _Nullable)password
error:(NSError **)error;
// Deprecated:
+ (DigipassSDKGenericResponse * _Nullable)validatePasswordWithFingerprint:(NSString * _Nullable)platformFingerprint
staticVector:(NSData *)staticVector
dynamicVector:(NSData *)dynamicVector
encryptionKey:(NSData *)encryptionKey
password:(char * _Nullable)password
error:(NSError **)error
__attribute__((deprecated("Use validatePasswordWithFingerprint:staticVector:dynamicVector:password:error: instead")));The returned values are identical for the old and new method, i.e., the behavior remains unchanged.
Fixes and other updates
Android
[MSS-12823]: Incorrect flow sequence
Description: The SDK tried to first decrypt a message and threw the SECURE_CHANNEL_DISABLED error when the Digipass authenticator was not activated. While the error itself was expected, the error message was misleading.
Status: This issue has been fixed. The flow sequence has been corrected. The SDK now checks the activation status before attempting to decrypt the message. If any of these operations fail, the SDK now returns the correct error code.
[MSS-12926]: Technical documentation updated
Description: The API documentation that is included in the product package has been updated for the isSecureChannelEnabled() method and now explains the correct method behavior. Also, the documentation was generally improved and typos fixed to enhance overall accuracy.
[MSS-12991]: Incorrect information for crypto app index
Description: When the crypto app index had a mismatch, the SDK returned an incorrect error code.
Status: This issue has been fixed. A new error code was added for this type of incident, INVALID_AUTHENTICATION_MODE (-4088).
iOS
[MSS-11227—Support case INC0014554]: Misleading information in technical documentation
Description: The technical documentation included in the product package instructed the user to store the dynamic vector in local storage. This information was not accurate and misleading.
Status: This issue has been fixed. The misleading information has been removed.
Supported platforms
For information on the supported operating systems and platforms supported by Mobile Security Suite and the affiliated SDKs, see Supported platforms.
Known issues
For information on issues that have not yet been resolved in this release of Mobile Security Suite, see Known issues.
API reference documentation and sample applications
To learn more about the public APIs and their functions, exceptions, and error codes, refer to the technical documentation that is included in the product package for each SDK and each platform. In the product package, you can also find the sample applications provided for each platform to see examples of how the SDKs can be used.
These sample apps are intended only to demonstrate basic scenarios and SDK usage. They are not designed to be copied directly into production projects!
Third party licenses
For information on third party dependencies associated with Mobile Security Suite and the affiliated SDKs in this release, see Third party licenses.