What's new in the Digipass SDK

This section provides an overview of changes introduced in the Digipass SDK to facilitate the integration of the SDK and provide information on backward compatibility.

Previous versions

Version 4.32.0

iOS

Bitcode support has been eliminated

Following the deprecation of Bitcode by Apple, we no longer support and have removed all Bitcode from the SDK framework.

Version 4.31.1

Android

Target API increased to 33

To meet new requirements for apps published on the Google Play Store, the target version of the SDK has been increased to Android 13 with API level 33. This change is needed to avoid APK rejection caused by security issues found with older API versions.

iOS

API updates – NErrors API support for Objective-C added

In version 4.30.1 of the SDK, the NError support for Objective-C was added. With this, the Objective-C API points no longer throw an NSException.

If an error occurs, the response object will be null. The dynamic vector will be attached to the error object so it can still be saved in the secure storage.

For more information, see iOS and the Objective-C and Swift samples included in the product package for full code examples.

Version 4.31.0

Android

Increased the target API to Android 12

To meet new requirements for apps published on the Google Play Store, the target version of the SDK has been increased to Android 12 with API 31. This change is needed to avoid APK rejection caused by security issues found with the old API versions.

Increased the minimum supported version to Android 6

The minimum supported version has been increased to fully support new features and devices. Deprecated code has been replaced and simplified to be compatible with API 23 or higher.

iOS

Fixed internal error conversion issues

Error codes converted between Objective-C and Swift need to have the NSCustomError setting implemented to display the correct value. Without this setting, the wrong codes could be displayed from the enum. The setting has been implemented in all the remaining error handling objects.

Increased the minimum supported version to iOS 13

The minimum supported version has been increased to fully support all arm64 devices and SwiftUI features. Deprecated code has been removed and replaced with code fully supporting iOS 13 or higher.

Version 4.30.1

Android

Delivering AAR file instead of JAR

AAR files are the current standard for Android libraries. For this reason, the JAR file has been replaced with an AAR file. For more information, see Integrate the Digipass SDK with Android or refer to the sample included in the product package.

iOS

API updates – NErrors API support for Objective-C added

The Objective-C API points no longer throw an NSException. All API points that previously would throw such an NSException now require an NSError pointer. If an error occurs, it will be attached to the pointer that is provided as parameter. Refer to the Objective-C sample included in the product package for full code examples.

Change of framework name to MSSDigipass

The framework name has been changed from DigipassSDK to MSSDigipass. To use the new Objective-C API, replace all previous DigipassSDK imports with #import <MSSDigipass/MSSDigipass.h>. The old C API is still available. To use it, replace the DigipassSDK imports with #import <MSSDigipass/DP4Capi.h>.

Using char byte array to store the password

The string password is now replaced with a char byte array. This change applies to both the Swift and Objective-C APIs. For information how to use the char byte array password for Digipass, refer to the sample included in the product package.