Swiftpack.co - Swift Packages by digime

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - Base url path is added to the SDK config file. - 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 **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 ## New Features - SDK can now be installed as Swift Package. - Removed unnecessary optional `publicKey` property on `Configuration` object. - Removed dependency on SwiftJWT ## 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](https://digime.github.io/digime-sdk-ios/getting-started.html) - 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. ## 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](https://digime.github.io/digime-sdk-ios/ongoing-postbox.html) 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](https://digime.github.io/digime-sdk-ios/migration-tips.html). - 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](https://digime.github.io/digime-sdk-ios/Classes/DMEPullClient.html#/c:objc(cs)DMEPullClient(im)authorizeWithOptions:completion:) 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. - Added support for Ongoing Access. See [documentation](https://digime.github.io/digime-sdk-ios/ongoing-access.html) 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. Updated API certificates in the SDK. ## Features - `DMEScope` has been extended to support a more granular level of data fetch. You can now limit your request to just Social data, for example. You could even go as far as to restrict your query to 'Spotify play history from the last 24hrs only'. Check out the changes in the docs, [here](https://digime.github.io/digime-sdk-ios/scope.html). - We've exposed some of the internal workings of `DMEPullClient` publicly, so you can take finer control over what data is or isn't downloaded, should you want to. - You can now customise the underlying polling logic in `DMEPullClient` by modifying `pollInterval` and `maxStalePolls` in `DMEPullConfiguration`. ## Comments This release changes the signature of the `getSessionData` method. The second lambda now has two parameters, so you may experience a compilation error on updating. Capturing the second parameter (the complete file list) resolves this error.