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

Version 5.9.0

Android

Target API level increased to Android 14 (API 34)

The target version of the SDK has been increased to Android 14 with API level 34.

Previous versions

Version 5.8.1

iOS

Retrievable property removed

For the OneSpan Client Device Data Collector (CDDC) SDK, the Keyboard identifier property has been removed from the retrievable device and event properties for iOS due to a new limitation introduced by Apple.

Privacy manifest updated

The privacy manifest for the Orchestration SDK has been updated. The SDK can use geolocalization to track the user for analytic and security-related purposes. This applies to both coarse and precise geolocalization.

Version 5.8.0

All platforms

API improvement for crypto app indexes

The name and value names of the API crypto app indexes have been unified and now have the same names as used by Digipass:

  • Name: CryptoAppIndex (instead of CryptoApplicationIndex)

  • Value:

    • Android: appnumber or, on Java, APP_1, APP_2 etc. (instead of FIRST, SECOND, THIRD etc.)
    • iOS (Swift): appnumber (app1, app2 etc.) (instead of indexnumber)

Android

CDDC keys deprecated (MSS-8259)

For the CDDC SDK, a number of properties and their corresponding setters have been deprecated and will be removed in a future version. With this, the following properties and setters will also be no longer available for the Orchestration SDK:

  • Native code hooks
  • Application repackaged
  • Debugger attached

iOS

CDDC keys deprecated (MSS-8248)

For the CDDC SDK, a number of properties and their corresponding setters have been deprecated and will be removed in a future version. With this, the following properties and setters will also be no longer available for the Orchestration SDK:

  • Rooting probability
  • Root status
  • Untrusted keyboard
  • Untrusted screen-readers
  • Native Code hooks

The Root status (Key 15) property and its corresponding setter has been renamed for iOS to DeviceJailbroken.

Version 5.7.0

Android

Updated readme file

The readme file in the product package has been improved to include more comprehensive steps and configuration options.

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 5.6.3

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.

Version 5.6.2 (hotfix)

Access Group required for orchestration

On iOS, to avoid an issue reported by a customer related to the Device Binding Access Group, we introduced a change in the implementation procedure. As of this release, it is mandatory to provide an access group when creating an orchestration. For existing integrations, the AppPrivate access group must be used for activated users when creating an orchestration.

Version 5.6.0

Android

Target API increased to Android 12 (API 31)

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 or higher. This change is needed to avoid APK rejection caused by security issues found with the older API versions.

Minimum supported version increased to Android 6 (API 23)

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

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.

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.

Version 5.5.1

Android

Maven repository

The Orchestration SDK and its Mobile Security Suite dependencies are now delivered exclusively through a local Maven repository. Due to this, you need to perform the following steps:

  • Indicate the URL to the maven folder in the gradle as an available repository.

  • Indicate the Orchestration SDK as a dependency with the following line:

    api 'com.onespan:sdk_orchestration_android:<version>'

Refer to the Android sample included in the product package for full code examples.

iOS

Change of framework name to MSSOrchestration

The framework name has been changed from OrchestrationSDK to MSSOrchestration. To use the new Objective-C API, replace all previous OrchestrationSDK imports with #import <MSSOrchestration/MSSOrchestration.h>.

API updates – NSErrors 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 a parameter. Refer to the Objective-C sample included in the product package for full code examples.