Version 5.1.0

• iOS digiMe SDK split into three separate modules: DigiMeCore, DigiMeHealthKit, and DigiMeSDK, allowing developers to add Apple HealthKit functionality only if needed. Apple checks if your app includes HealthKit dependencies but is not related to health and fitness. This architecture resolves that issue.
• Apple Health now supports not only Activity Summary JFS objects within the web flow but also simplifies direct access and HealthKit data retrieval by reusing boilerplate code in the SDK to execute HealthKit queries.
• Discovery sources support within the SDK.
• Provisional Cloud Storage support.
• Improvements to the delete library functionality.
• Introduced the Reauthorize Sources functionality.
• Bug fixes.

Version 5.0.5

• Base url path is added to the SDK config file.

Version 5.0.4

• File download operation will return all errors of SDKErrors type.
• Handle metadata headers as case insensitive in file download route.
• retryafter will be the optional property

Version 5.0.2

Bug fixes:
Support for Sync Status Error in parsing File List response

Improvements:
Example apps minor updates.

• Genrefy supports Saas SDK
• SDK Example app - supports ObjectType Scope

Version 5.0.1

New Features

• SDK can now be installed as Swift Package.
• Removed unnecessary optional publicKey property on Configuration object.
• Removed dependency on SwiftJWT

Version 5.0.0

New Features

• SDK is updated to utilise new digi.me SaaS offering, with the ability to use digi.me without installing a separate digi.me application. Documentation can be found here: Getting Started

• Support read flows:

  • Ability to ask a user to authorize sharing of data.
  • Ability to ask user to onboard services and share them using digi.me on an ongoing basis.
  • Ability to read data that you’ve pushed in to a user’s digi.me library.

• Support write flows:

  • Ability to write data to user’s digi.me library.

• You can request any data to be deleted from a user’s digi.me library.

Other Notes

• This release introduces breaking changes to users of version 4.0.0 of the SDK.
• Support for previous flows using digi.me clients have been dropped in this version.

Version 4.0.0

New Features

• Introduces support for Ongoing Postbox (data pushes to user), which allows SDK to push data to user over multiple sessions after being granted user's consent just once. See documentation for details.

This only works with ongoing push contracts. One-off push contracts can still use the existing Postbox functionality..

Breaking Changes

• DMEPushClient must now be created with a configuration which includes the contract's private key.
• All SDK function completion blocks will now be performed on the main thread. This is to provide consistency across the SDK.
  See migration tips.

Version 3.3.0

• Introduces a new DMELimits object with duration property which can be used to either declare whether app wants to wait for fresh data or declare how much time (in seconds) the app is willing to dedicate to fetching latest data. See documentation for details.

• authorizeWithScope:completion: and authorizeOngoingAccessWithScope:oAuthToken:completion: in DMEPullClient have been deprecated. They are now replaced with authorizeWithOptions:completion:] and authorizeOngoingAccessWithOptions:oAuthToken:completion which introduces a new DMESessionOptions object containing the existing DMEDataRequest scope and the new DMELimits object.

• Updates backend API version to use.

NOTE: If you are using Ongoing Access, you will need to update to this version of SDK in order to continue using it.

Version 3.2.0

• Added support for Ongoing Access. See documentation for details. In short, provided you have the necessary contract setup, you no longer need to open digi.me app to get new data after initial consent.
• Added Genrefy app to showcase Ongoing Access.

Version 3.1.1

Updated API certificates in the SDK.