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.
Developers now have the ability to continuously push data to digi.me once the user has granted consent to on-going access without digi.me client app involvement.
Other changes.
Functions have been moved to provide a more logical SDK structure. Please see the documents to see how the SDK is now structured.
The SDK now uses named parameters. Developers upgrading to this version need to ensure when calling the functions, parameters are passed correctly.
A new function prepareFilesUsingAccessTokenhas been extracted out of authorizeOngoingAccess. To prepare data for private share when you already have an access token, you can call this new method. This avoids the need to provide parameters used only in authorization.
getSessionData function now returns a Buffer as output instead of a base64 string as before.
You’ll need a private key when pushing data to a postbox. pushDataToPostbox method is updated to require this. The file to be pushed in is expected as a buffer object instead of a base64 string before.